Hi Inel,

I just wanted to let you know that we have now released LogViewPlus v2.4.42 into BETA available here:
https://www.logviewplus.com/download.html

This release includes fixes for a number of the issues discussed in this thread:
 - Refreshing a log file with a running session now displays all log entries.
 - Negative elapsed times will now be displayed correctly.  Note that sorting does not impact elapsed times.
 - Adding lines in the format "\n<Message>" is now handled correctly.  This was the core problem discussed in the thread.

After further investigation the "sorting by date" issue is not a bug.  The issue here is that the date and time columns are related.  When you sort by date, you are really sorting by date and time.  This leads to the second sort column seeming appear out of order, but what is really happening is that there are very few entries for a given timestamp. 

Thanks for bringing these issues to my attention. Please let me know if you have any further questions or issues.

Toby

Thanks Inel - I am able to recreate the issue now.  Let me take a look and see if we can get this fixed for the next release.

Thanks for bringing this problem to my attention!

Toby

Hello Toby,

It seems the issue appears when sorting starts with date / time.

Of course, we will create separate threads for any further reports.

Hi Inel,

When I test, this feature seems to be working correctly:




This might have something to do with the data types of the columns you are sorting.  If you can give me more detail, I can try to recreate on my end.

Also, in future it would be best to create new threads for new issues.  This helps to keep the conversation focused and makes it a bit easier to track what has / hasn't been fixed.

Thanks,

Toby

We just tried sorting your DX grids by multiple columns, which is also useful in certain cases, but does not seem not work (you can shift-click on additional columns and the sorting indicator appears as usual, but no further sorting occurs). Is this expected if you are perhaps implementing CustomColumnSort, or could this be made to work?

I am able to recreate the "All new log entries" issue.  I will get this fixed for the next release as well.  Thanks for bringing this it my attention.

Elapsed times are calculated as the absolute time between a given log entry and the previous log entry in the view.  Sorting does not change the elapsed time.

I can see where a negative elapsed time value might be helpful.  I will look into this for the next release.

Thanks again,

Toby

Hello Toby, some other issues do seem to stem from this, some probably not.
The only one i can reproduce at the moment is what i would consider unexpected behaviour:
Open a file, start a session, then reload the file (on either session or file view context menu). The session then states "All new log entries", so you would expect new entries to show up there, however they go under the underlying view from that point on.
There is also something else we noticed - elapsed times are calculated as an absolute value and only when they are added instead of being a calculated value or refreshing upon sorting. So if you have entries that have timestamps out of order in respect to line order (which can happen in certain cases), they should show the relevant difference to the prior entry (so negative values should be possible) and if the entries are reordered (usually you would want them ordered by timestamps), the elapsed values should be recalculated. Examples of what i mean by this in below screenshots.

Thanks for the update.  

I am able to recreate the behavior described by not including a newline after a log message.  In other words:
<LogLine>\n  - Works as expected.
\n<LogLine>  - Recreates the issue described.

I will need to investigate this and get back to you.  This looks like a bug and something that will need to be fixed in the next release.

This issue is specific to the most recent log entry.  You have reported a number of different issues in this thread and I am wondering if they all stem from this problem.  Have the other issues been resolved?  Do the other issues appear related to this cause?

Thanks for reporting this issue!

Toby

The messages show up as separate entries. Screenshots below to clear up any misunderstanding.
Starting state:

Added message 2 and saved (message 2 missing in LVP):

Added message 3 and saved (message 2 and message 3 now show up at the same time in LVP):

Selected entries in code so you can see the tabs are there as they should be for parsing.

Thanks for the update.  I have replaced the 4 spaces to use three tabs.  When I do this, I can parse the file with:
%d{yyyy-MM-dd %H:mm:ss.fff}\t\t\t[%p]\t\t\t<%t>\t\t\t%m%n



Is this what you expected?  

Tabs are similar to spaces in that, if three tabs are expected, three tabs will always need to be found.  Maybe the problem is that the number of tabs can fluctuate?

Also, LogViewPlus should never 'skip' a line.  If a parser is configured incorrectly, I would expect the data to be included as part of the previous log entry.  It can still be found with a text search.  This might be the problem you are describing with "Both message 1 and message 2 will now show."