Output Messages Window: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Currently, ParaView's Output Window for messages from its internal code are text only, | |||
presenting the whole information that may be useful to a developer. | |||
The current output window has several drawbacks: | |||
- A message always contains the whole information, making it hard for users that do not | |||
need that to extract the relevant parts. | |||
- If messages are reported several times from the application, they are | |||
printed several times in the output window. | |||
As an example we show the output window after an nonexistent variable is typed in the | |||
Calculator window. | |||
[[File:output-window-original.jpg]] | [[File:output-window-original.jpg]] | ||
We plan to redesign the Output Window to address these issues as follows. | |||
By default, | |||
[[File:output-window-short.jpg]] | [[File:output-window-short.jpg]] | ||
[[File:output-window-long.jpg]] | [[File:output-window-long.jpg]] | ||
Revision as of 20:17, 16 January 2015
Currently, ParaView's Output Window for messages from its internal code are text only, presenting the whole information that may be useful to a developer. The current output window has several drawbacks: - A message always contains the whole information, making it hard for users that do not
need that to extract the relevant parts.
- If messages are reported several times from the application, they are
printed several times in the output window.
As an example we show the output window after an nonexistent variable is typed in the Calculator window.
We plan to redesign the Output Window to address these issues as follows. By default,
