| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001039 | OMNeT++ | runtime / Qtenv | public | 2018-05-16 10:03 | 2018-05-16 10:03 |
|
| Reporter | attila | |
| Assigned To | attila | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | 5.3 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001039: Log output filtering based on module is confusing |
| Description | The filtering in the module output (log) mode of the Log Inspector in Qtenv works in mysterious ways.
It is not clear which module is considered during filtering: the one that processes the current event, or the one that does the actual logging (see Enter_Method() for why these might not be the same).
The behavior of the filter in this regard should be clear to the user. It might have to be adjusted as well, to make it more usable/intuitive/logical/configurable/etc. Then it should be documented (at least a note in the dialog).
Also, in some cases (during network initialization, and inside method calls) the same module path is prefixed twice, with different color. |
| Steps To Reproduce | Run any non-trivial INET simulation with mobility and/or 802.11, and fiddle with the module filter of the log output window. |
| Additional Information | See original report and some explanation here:
https://groups.google.com/d/msg/omnetpp/fkQkDilZJ0o/qneZ3O8kCQAJ [^] |
| Tags | No tags attached. |
|
| Attached Files | |
|
Relationships 
Relationships 