ihsoft / kspdev Goto Github PK

At the very least via as settings file.

Sometimes it makes sense to block clicks going thru the console. As well as mouse zooming.

A simple filter field to work with the logs currently captured by the aggregator. It can be used to quickly find the records that are relevant to a specific module. The search is done by prefix on the source name, case-insensitive.

The controls of the console (buttons, filters, etc.) are located at the bottom of the window. When the window is dragged down the controls become invisible. This is a pretty usual operation, but it makes using console hard. This can be improved by moving the controls at the top of the window depending on the current position.

When a record is selected allow expanding the stack trace data with the relevant assemblies paths. It may greatly help to troubleshoot which mod triggered the issue.

Allow the console window to have different sizes.

Hey ihsoft, I'm working on making some offline backups of KSP wikis that I often reference or expect to reference (since Internet access is sometimes a little flaky where I live), but one of your wiki pages (https://github.com/ihsoft/KSPDev/wiki/ReleaseBuilder:-Schema-1.0) has a colon in it, which causes Windows to choke on it while cloning. Can you please change that?

KSPDev_LogConsole 0.19 contains KSPDev_Utils 0.35 instead of 0.37

As for now UI allows silencing a source but not the opposite action. The only way to unsilence is editing the settings file.

Since only description is used to make a hash it may happen that standard exceptions from different source get grouped. E.g. NRE has the same description of any occurrence.

Allow configuring how many logs to keep, and make mod cleanuing up obsolete files. Could be just a run counter, or a time limit, or both.

When shape is a cylinder, and it's not aligned along one of the axis the calculated bounds are wrong.

The source is aligned in the same look direction as the target. However, they should "look" at each other, i.e. the directions must be the opposite.

Exception's stack trace is passed as a string in the handler argument. Splitting it by lines should give the same picture as stack trace object in normal messages.

Related to #1.

Would require KSPDev utils update.

When a key is released outside of the game application, the switch doesn't notice the release event. As a result the switch assumes it's in hold state.

Example. Switch from the game using alt+tab, and return back by clicking the app on the taskbar. The switch for the alt key will stay in the hold state.

As for now it can only be done via settings file.