Threads are shown in date order by default.  What you are trying to do here is group thread activity while sorting the groups by characteristics of data within a group.  This is a new suggestion for us.  Above I suggested a new feature rather than something you could try right now.  Sorry this was not clear.

I was thinking we could create thread filters in a specified order.  This approach would give users a great deal of flexibility in how filters are created.

For example, you could write a query like:  select Thread from CurrentView order by Timestamp.  Each Thread returned by the query would indicate a new filter to be created.

This suggestion works with filters rather than groups.  This fits better into the model of how LogViewPlus works with data.

Groups in LogViewPlus are more about getting familiar with a dataset.  This is why they are ordered alphabetically and display a record count.  Groups do not feed into other LogViewPlus actions such as sub filters or reports.

Hi again

We find a workaround.
As i said previously we add an external command in your tool (to process file before opening it) that change threads to include message of first line of each thread to make the threads grouping more readable.

We tune this tool to add a prefix in each thread to force the alphabetically order to follor the date order.
Like this:


The number {xx} is linked to date time
This work. Not in the beauty of the art but it works.

We still have an issue that ordering of collapsed thread is ONLY in ascending order (that is here in ascending date) and nothing else.
But at least this makes the job

Hi again

To come back to your filter story above, do you have any recommendation to have a view, using sql filters, to group lines by Thread but ordered by date ?

Thanks

Glad to hear you found a solution Eric - thanks for letting me know!

I am still trying to think of ways to create an ordered list of filters.  I think the best way to work this into the application would be to create a new rule type.  Something like 'Create filters from SQL statement'.  This may be something we could look into for the next release.