gachl / cm-ss13-logger Goto Github PK

When a weapon is used in melee combat against a xenomorph each attack will dull / melt the weapon due to their acid blood. This would reduce the damage of the weapon after each and every use. This could also be applied to PBing with guns, as acid splash would logically do damage to the weapon.

The more rows use a font style different than the default the worse performance gets.

This is not a problem during regular operation. If the program has been running for a while with a lot of log messages restarting and skipping the log will fix the performance again.

It's a problem when replaying a whole log file, very quickly the updating speed gets very low.

Tried handling this with a font cache and reduced assignments however I think it has something to do with how DGVs are rendered, maybe instead of a DGV another display method needs to be found.

Highlighting rules should be case-insensitive.

Additional checks have to be performed before calling FirstDisplayedScrollingRowIndex as it can still throw exceptions, like when a DataGridView is not visible.

Give the option to switch between different configuration files for easier handling when changing roles.

• Tab order
• Alt codes
• Hotkeys
• Expand columns to full width in editors
• Add icon

Some formatting tags like <i> are being displayed in messages. This stuff should be truncated or used to invoke a transistent highlighting rule for the row that it could default to if no other highlight has been found.

Instead of only applying the first highlighting rule, give rules a "Stop at this rule" option and apply all matching rules in order additively.

To load a different log file the user has to restart the program. There should be a way to load a new log without having to restart.

• Modal dialogs are blocking interaction, this is not useful.
• Dialogs are shown on the parent center which hides them if the main window is in topmost mode.

It should be possible to keep the window as the topmost window so that it can cover parts of BYOND for single screen usage.

Some log messages are multiline, add support for these.

To implement, keep a history of past log messages (up to a limit) and apply regular expressions against the concatenated history and message.

Move up and down buttons should be added since highlighting rules are order depended.