View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0015240 | ParaView | (No Category) | public | 2015-01-05 16:34 | 2015-09-06 12:17 | ||||
Reporter | Ken Moreland | ||||||||
Assigned To | Dan Lipsa | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | 4.4 | Fixed in Version | 4.4 | ||||||
Summary | 0015240: Hide some diagnostic information in output window | ||||||||
Description | Currently the output window is a raw dump of every error and warning that is issued from the VTK layer. Each one almost always comes tagged with a bunch of information (source file, line number, class name, object pointer) that is meaningless to any user that is not actively developing that code. This makes the errors and warnings much harder to read (and hence much less useful when they occur). For example, let's say that the user mistypes something into the calculator filter. The output window will pop up with the following intimidating text: ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, line 1455 vtkFunctionParser (0x7f9ce49ae890): Syntax error: expecting a variable name; see position 0 ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, line 1455 vtkFunctionParser (0x7f9ce49ae890): Syntax error: expecting a variable name; see position 0 Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Filters/Core/vtkArrayCalculator.cxx, line 421 vtkPVArrayCalculator (0x7f9ce49ae060): An error occurred when parsing the calculator's function. See previous errors. That is way to verbose for a simple error that is easily corrected (once a user figures out what is going on). It would be much more effective to have output like the following: Syntax error: expecting a variable name; see position 0 [2 occurrences] [Details] An error occurred when parsing the calculator's function. See previous errors. [Details] As you can see, simply by removing the extraneous information, the error becomes much easier to understand. Each entry should also have some GUI element that allows you to see the full details. (The two syntax errors have also been combined to one per bug 0015239.) Almost all VTK messages use the same format (created by the vtkError/WarningMacro), so parsing this information should be very easy. It is probably worth playing with different GUI widgets to use to display the information. A text or html box might be fine, but a table or hierarchical view might work better. | ||||||||
Tags | No tags attached. | ||||||||
Project | Sandia | ||||||||
Topic Name | output-window-15240 | ||||||||
Type | feature | ||||||||
Attached Files | |||||||||
Relationships | ||||||
|
Relationships |
Notes | |
(0034016) Alan Scott (manager) 2015-01-05 17:20 |
I am targeting 4.4, since this has been an ongoing issue in many locations of the code. |
(0034120) Utkarsh Ayachit (administrator) 2015-01-29 08:03 |
------------------------------------------------------------------------------ | * b8d9b75 (stage/output-window-15240) Fix compilation warnings. | * 06373bf Move VTK: 'Accumulate strings printed to console by Python' | * 0305931 ENH: Parse, colate and filter output messages. ------------------------------------------------------------------------------ |
(0034127) Utkarsh Ayachit (administrator) 2015-01-29 08:06 |
SUMMARY --------------------------------------------- Topics merged into master (v4.3.1-83-gf35be3b): 14953_fix_Esc_key_in_settings_dialog 14957_fix_settings_segfault 15031_fix_multicore_mode 15283_fix_camera_settings_importation 15293-guard-interactive-rendering bag-plot cosmotools-filters-xml fix_mpi_link_issues (VTK) output-window-15240 (VTK) pvweb-loadsave-state-and-save-data pvweb-merge-sources-filters |
(0034236) Alan Scott (manager) 2015-02-18 15:43 |
Sweet! Tested master, Linux, remote server. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-01-05 16:34 | Ken Moreland | New Issue | |
2015-01-05 16:37 | Ken Moreland | Relationship added | related to 0015239 |
2015-01-05 17:20 | Alan Scott | Note Added: 0034016 | |
2015-01-05 17:20 | Alan Scott | Target Version | => 4.4 |
2015-01-07 14:39 | Dan Lipsa | Assigned To | => Dan Lipsa |
2015-01-07 14:39 | Dan Lipsa | Status | backlog => active development |
2015-01-29 08:03 | Utkarsh Ayachit | Topic Name | => output-window-15240 |
2015-01-29 08:03 | Utkarsh Ayachit | Note Added: 0034120 | |
2015-01-29 08:03 | Utkarsh Ayachit | Status | active development => gatekeeper review |
2015-01-29 08:03 | Utkarsh Ayachit | Fixed in Version | => git-next |
2015-01-29 08:03 | Utkarsh Ayachit | Resolution | open => fixed |
2015-01-29 08:06 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
2015-01-29 08:06 | Utkarsh Ayachit | Note Added: 0034127 | |
2015-02-18 15:43 | Alan Scott | Note Added: 0034236 | |
2015-02-18 15:43 | Alan Scott | Status | customer review => closed |
2015-06-15 08:02 | Utkarsh Ayachit | Fixed in Version | git-next => git-master |
2015-09-06 12:17 | Utkarsh Ayachit | Fixed in Version | git-master => 4.4 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |