OMNeT++/OMNEST Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001046OMNeT++runtime / Qtenvpublic2018-07-26 05:392018-08-01 17:08
ReporterManiAm 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0001046: sort event pane by columns
Description[feature] ability to sort the events by clicking on each column.
TagsNo tags attached.
Attached Filespng file icon 2018-07-25_22-34-44.png [^] (241,768 bytes) 2018-07-26 05:39

- Relationships

-  Notes
(0001366)
attila (developer)
2018-07-31 11:43

Could you please elaborate a bit on what exactly you would use this for?
Is it possible that some filtering would be enough instead?

I'm asking because the current implementation is heavily geared towards scalability in the number of log entries in the buffer. For this, and some other reasons, adding something like sorting to this inspector would require significant effort. Filtering functionality is already in place, so extending that to be more useful should be less painful.

On top of this, once the order of the entries can be different than in which the events occurred, the display might become confusing to the user - for example if the sorting is stored across executions, but the user forgets that they changed it sometime in the past, and now wonders why the entries are all mixed up.
(0001367)
ManiAm (reporter)
2018-08-01 17:08

>> Could you please elaborate a bit on what exactly you would use this for?

To group related entries together. For example, if I am interested in OSPF hello messages, then I click the 'Name' to group all hello message exchanges between all nodes. Can we do this using filtering? I don't think so.

>> but the user forgets that they changed it sometime in the past ...

The Qtenv can reset this feature to default upon each execution. If the user needs to sort entries based on a column, then he needs to activate it again.

>> I'm asking because the current implementation is heavily geared towards scalability in the number of log entries in the buffer.

I understand. This is a (nice to have) feature, but if it hurts the performance under the hood, then you can just ignore it :)

- Issue History
Date Modified Username Field Change
2018-07-26 05:39 ManiAm New Issue
2018-07-26 05:39 ManiAm File Added: 2018-07-25_22-34-44.png
2018-07-31 11:43 attila Note Added: 0001366
2018-08-01 17:08 ManiAm Note Added: 0001367


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker