Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#3607 closed enhancement (fixed)

Message number reset

Reported by: anonymous Owned by: Adeel Asghar
Priority: normal Milestone: 1.9.4
Component: OMEdit Version:
Keywords: Cc:

Description

When a user checks a model he can receive several error messages.
Currently it is not easy to see how many of them are present, since the error count is not reset before every model checking action.

I propose to change the checkbox in OMEdit Options|Messages from
"Reset messages number before simulation"
into
"Reset message number before model check or simulation".

In this way at every "Check" or "Simulate" request the error message is reset before checking or simulating action occurs.
I suggest also to leave that checkbox checked as default.

Change History (10)

comment:1 by Adeel Asghar, 9 years ago

Resolution: fixed
Status: newclosed

Done in e5e5bfe/OMEdit.

comment:2 by Dietmar Winkler, 9 years ago

Milestone: Future1.9.4

Sorting these closed tickets away from "Future". Since they were closed after the last 1.9.3 release, it's very likely that they should have been part of the 1.9.4 release.

comment:3 by anonymous, 9 years ago

It seems to me that error message number is not reset, even if the checkbox you've added in Options|Messages is checked!

comment:4 by anonymous, 9 years ago

Resolution: fixed
Status: closedreopened

comment:5 by Adeel Asghar, 9 years ago

Error message number will always reset if you have checked Reset messages number before checking, instantiation && simulation.

https://trac.openmodelica.org/OpenModelica/browser/OMEdit/OMEdit/OMEditGUI/MainWindow.cpp#L797

Can you provide a case where it is not working for you? Note that it will only reset for checkModel, instantiateModel and translateModel.

comment:6 by anonymous, 9 years ago

It was my fault. But I want to clarify

Consider this situation:

  • you check a model and get an error.
  • you now check another model that is ok. Since no error is detected, the message browser window shows previous messages in red.

I did not read the details of the message, that referred to the previous check (and previous model).

Maybe it is better to show in the browser window, in red, a message when a check is successful?
I propose to replicate there the first row of the dialog box that opens when a model is succesfully checked.

So the user, that reads the last rows, first, when looking at the message browser will have immediate feedback of the positive result of the check and will not be misguided by the bright red of latest messages.

comment:7 by anonymous, 9 years ago

CORRECTION OF THE PREVIOUS MESSAGE
It was my fault. But I want to clarify
Consider this situation:
you check a model and get an error.
you now check another model that is ok. Since no error is detected, the message browser window shows previous messages in red.
I did not read the details of the message, that referred to the previous check (and previous model).
Maybe it is better to show in the browser window, in black, a message when a check is successful?
I propose to replicate there the first row of the dialog box that opens when a model is succesfully checked.
So the user, that reads the last rows, first, when looking at the message browser will have immediate feedback of the positive result of the check and will not be misguided by the bright red of latest messages.

comment:8 by Adeel Asghar, 9 years ago

Resolution: fixed
Status: reopenedclosed

Done in 86b0320/OMEdit.

comment:9 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.4-1.9.x

Milestone renamed

comment:10 by Martin Sjölund, 9 years ago

Milestone: 1.9.4-1.9.x1.9.4

Milestone renamed

Note: See TracTickets for help on using tickets.