Yep. That worked. Not most intuitive... I would have liked to have something explicit.

Thanks for the feedback Meni.  We will be making some changes to how columns are saved in 2022.  I will see what can be done about making this process more intuitive.

Toby

I want to +1 this request and also ask that the columns settings can be saved on a per-merge and per-filtered view basis.

It'd also be great if I could save column visibility/position sets that can I can apply to views as I sometimes need different views of the same logs.

Thanks for the feedback.  It's helpful when determining which features to work on. 

Columns in LogViewPlus are currently saved as part of the parser configuration.  This ensures that files 'of the same type' have the same column headings.  It would be great if we could provide more flexibility here while increasing usability.  Saving column settings with a workspace might be one way to do that.