I guess you got it working then.  :-) Thanks for the feedback Bill!

AWESOME!!

Hi Bill,

Today we released a new BETA version of LogViewPlus (v2.4.21) which allows you to force LogViewPlus to sort log entries when they are loaded.  Under Tail Settings, there is a new option to "sort log entries by date in ascending order".



The BETA release is currently available on our download page at: https://www.logviewplus.com/download.html

Thanks again for the feedback!

Toby

Thanks Bill.  I will add this feature into the next release and post back here when it is available for testing.

Thanks for the feedback!

Toby

Great to hear!
Yes I believe the "Sort log entries after......"​ would be great.
Having the order retained is the big thing. Clicking to change order is not a big deal if retained, being able to configure it would just make it that much easier.​
Thanks again!,
Bill​​

Hi Bill,

Thanks for the sample files.  I was able to recreate and fix the issue.  We will release this in the next beta release - hopefully in the next 2-3 weeks.

Regarding the "startup sort order" discussion we had above.  LogViewPlus does not sort log entries unless they are merged.  It displays them as they are written to the log file.  In this case, they are written in descending order (newest first).  This is a little bit unusual and contributed to my confusion.

With that in mind, I think the original feature request makes a lot more sense.  LogViewPlus assumes log files are sorted ascending order (oldest first) and some features, like tail, rely on this.  What we could do is add a configuration setting which forces LogViewPlus to sort log entries in ascending order on load.  This wouldn't break any existing functionality and would make all of your log files look like they are written in the same way.  The setting will be a check box asking, "Sort log entries after initial load?"  Or something.  You will not be able to set the sort direction.

Would that help?

Thanks for your help with tracking this issue down Bill!

Toby

Did not change anything.
Sent you the logfile we are viewing along with the parser settings.
Be interesting to see if you get the same results.
Thanks,
Bill G.

Thanks for the update.  Not sure what the problem could be.  I will need to take a closer look.

Can you please try one more thing?  For the pattern parser that fails, delete it and save your settings.  Then recreate it and try again.  Column settings are saved with the parser configuration.  I wonder if the column sorting has been saved incorrectly?

Thanks,

Toby

Ok, so tried to open some files with the basic parser and it does work correctly. Whatever order I select, stays selected.
So tried different files that use different parsers. A few file types did work correctly, but most don't. It does not seem to be parser type dependent.
I have three filetypes that work correctly, one with dsvparser, one xml, and the other with patternparser. The rest of them do not work correctly. They are a mix of pattern, dsv and 1 xml.

The only constant I can find is that if the file opens in any sortable format with the basicparser, it works as expected. I change the sort order and it stays the same when switching back and forth between file and filters. Filters are changed to match the order so all are the same. 
For all other parsers used....????

Also 1 or 2 files do open in the oldest to newest format....

Regards,
Bill

Well, now I am confused.  The default sorting should definitely be from newest to oldest.  Also, column sorting should preserved when navigating between views.

If I open a file with the BasicParser, this is what I see:



Can you please open a file with the BasicParser and confirm the dates are sorted newest to oldest?  Also, can you please confirm that column settings are preserved when navigating between filters when the BasicParser is used?  

I think the underlying problem here might be an issue with your parser configuration.  By using the BasicParser, we can test the theory.

Thanks,

Toby