logorrr.conf should be written after each relevant user interaction

[rladstaetter]

Currently, logorrr.conf is not always written after a user changes something in the application state. The idea is that the information in logorrr.conf should suffice to reinstate the application with the last known state.

For example, if you open a new file, logorrr.conf should also be changed.

It should also be documented somewhere what actions trigger a change in the configuration file.

[eitch]

This would be a really awesome feature. Especially, since my logs contain INFO, WARN, ERROR and not your default.

It would also be awesome, if one could change the color and/or text of an existing filter.

[rladstaetter]

well, if you exit LogoRRR and start again, already now LogoRRR will continue with the same files opened and the same settings used - but depending WHEN LogoRRR is exited this is not always correct.

The selection of filters and their persistence however is really a nuisance atm; works for me, but not necessarily for everybody else ;-)

Here I would like to introduce the concept of workspaces where you can save your favourite settings and also choose between different setups. I have to write those ideas down, would be cool if you could give me feedback here :)

[eitch]

Right, i was about to write it didn't save, but retried it, and it worked this time. Maybe i closed the file, then exited the app and then it didn't save?

Yes, I'll gladly give feedback on workspaces