By menihillel - 9 Dec 2021
Can we add support for this?
|
By LogViewPlus Support - 9 Dec 2021
Hi Meni,
I can see where this would be helpful and it is something we are considering. Application settings are due for a re-think. In particular, the current setup is very individual focused and we would like to move to a more team focused model. For example, it would be great if settings could be easily managed from a central location. This kind of setup would imply a lot more variation in parser and column configurations per log file.
We plan to address data manipulation and reporting issues first, but application settings management is definitely something we are thinking about.
Hope that helps,
Toby
|
By menihillel - 9 Dec 2021
Thanks Toby... as always. Very helpful to hear you are thinking about it and will consider this in future release. I've achieved the goal of seeding ... 
Love the product and the supreme support you've been providing.
|
By LogViewPlus Support - 9 Dec 2021
Thanks Meni. Glad to hear you are finding LogViewPlus helpful. :-)
Hopefully we can get some of these changes out in the second half of 2022. I will post back here when I have something for you in beta.
Toby
|
By menihillel - 20 Dec 2021
Hi Toby,
Is there a way to even persist columns globally? I finding myself repeatedly re-adding columns and readjusting their width.
|
By LogViewPlus Support - 21 Dec 2021
Hi Meni,
Column settings are persisted as part of the parser configuration. Files which use the same parser configuration will share the same column layout. Modifying the parser configuration will reset the column layout.
So, the only way to achieve this at the moment is to reuse your parser configurations more widely. Auto-generated parser configurations are not particularly good at supporting reuse, so there may be an opportunity to consolidate.
Hope that helps,
Toby
|
By menihillel - 21 Dec 2021
Unfortunately, it does not seem to work for me. I'm using multiple files, also merge, and two pattern parsers in a single workspace. I did not make any changes to the parsers, but still, every time I open thr workspace, all the columns layout gets reset.
|
By LogViewPlus Support - 21 Dec 2021
That's strange. What version of LogViewPlus are you using? Can you check the file properties in LogViewPlus and confirm the parser used is as expected?
Also, try opening and closing just a single file. I wonder if maybe the changes are getting overwritten some how.
|
By menihillel - 21 Dec 2021
Using latest. I've checked file properties and it indeed uses the right parser. The issue is with the fact it is automatic. At what point do you save layout? What if I resize? Add/remove columns? I cannot tell or force it to "save now". Again, I'm using merging... Maybe that's a hint.
|
By LogViewPlus Support - 21 Dec 2021
Saving is automatic when the layout changes.
Merge file settings cannot be saved because because there is no associated parser.
Try setting one file and see if those changes are persisted and restored correctly.
|
By menihillel - 21 Dec 2021
Yep. That worked. Not most intuitive... I would have liked to have something explicit.
|
By LogViewPlus Support - 22 Dec 2021
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
|
By sirlogalot - 15 Jun 2023
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.
|
By LogViewPlus Support - 16 Jun 2023
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.
|