User Issues: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
 
Line 4: Line 4:


== Dean Dobranich ==
== Dean Dobranich ==
{|
|- style="background:#abcdef"
! Issue
! Resolution
|-
| The Exodus reader did not give any status whatsoever when loading.
| Probably [http://www.paraview.org/Bug/bug.php?op=show&bugid=3426 bug 3426]
|-
| In order to show the color bar, we had to pull up the "Edit Color Map" dialog box. This checkbox should really be on the GUI under the "Display" tab. It was not until I got back to my office when I realized that there is a toolbar button to toggle the color bar, too. The button says "SbV", which means nothing, but I presume this will be replaced with an icon soon. However, the toolbar toggle status is not updated when the color bar is enabled with the dialog box.
| Toolbar button now has icon.
|-
| Lots of times the rendering went all screwy. It predictably happened when enabling the color bar through the "Edit Color Map" dialog box. It also happened when selecting cells through the rubber band select. The 3D rendering artifacts polluted the surface with black streaks. It may have been Z-buffer fighting. It may also have been the position, normal, and connectivity array information getting mixed up to generate oblong polygons and/or incorrect normals. I cannot replicate this behavior on my desktop. John predicts that this issue is caused by a 32-bit library accidentally linked into the 64-bit build.
| Wait for more stable build.
|-
| The red border around the active view disappeared.  It happened at the same time as the rendering problems.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=4171&pos=21 Bug 4171].
|-
| Dean has a feature request very important to him: the ability to select and cull an Exodus part by selecting it with the mouse. Dean visualizes Exodus data with, literally, hundreds of blocks. He has little notion of which blocks correspond to the parts on the screen. This feature could mean the difference between him using ParaView and him using something else.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=4169&pos=11 Bug 4169].  Deferred to ParaView 3.2.
|-
| Selecting cells did not fill the element inspector. I cannot replicate this problem on my Windows desktop.
| Wait for a more stable build.
|-
| There needs to be a way to add annotation that gives the current time.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=3058 Bug 3058].
|-
| The "Save Screenshot" function failed to make a valid .jpg or .png (or at least, one that can be read by xv). It works fine on my Windows desktop (when read back in with IrfanView).
| Works for me now.  Wait for a more stable build.
|-
| When "Save Screenshot" finally did save a valid image (to a .bmp file), it captured the file browser dialog box.
| Seems to work for the moment.  Releated to [http://www.paraview.org/Bug/bug.php?op=show&bugid=3924&pos=4 Bug 3924]
|-
| The block selection widget is not very friendly when trying to select a contiguous range of blocks (that is, do a shift click).
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=4173&pos=14 Bug 4173]
|-
| It is not evident what the "visible" option means for 3D widgets.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=4174&pos=12 Bug 4174]
|-
| When a new filter is created, the new data does not have the same coloring as the input data.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=3864 Bug 3864]
|-
| The threshold filter does not turn off the visibility of its input.
| [http://www.paraview.org/Bug/bug.php?op=show&bugid=3896 Bug 3896]
|}


== Mike Wong ==
== Mike Wong ==

Revision as of 18:21, 7 December 2006

This page captures a list of current issues that users have given us, catagorized by user. The intent is to "remember" the issues each user is facing and be able to present progress tailored to each user.

For the notes taken during the user interaction, see User Feedback.

Dean Dobranich

Issue Resolution
The Exodus reader did not give any status whatsoever when loading. Probably bug 3426
In order to show the color bar, we had to pull up the "Edit Color Map" dialog box. This checkbox should really be on the GUI under the "Display" tab. It was not until I got back to my office when I realized that there is a toolbar button to toggle the color bar, too. The button says "SbV", which means nothing, but I presume this will be replaced with an icon soon. However, the toolbar toggle status is not updated when the color bar is enabled with the dialog box. Toolbar button now has icon.
Lots of times the rendering went all screwy. It predictably happened when enabling the color bar through the "Edit Color Map" dialog box. It also happened when selecting cells through the rubber band select. The 3D rendering artifacts polluted the surface with black streaks. It may have been Z-buffer fighting. It may also have been the position, normal, and connectivity array information getting mixed up to generate oblong polygons and/or incorrect normals. I cannot replicate this behavior on my desktop. John predicts that this issue is caused by a 32-bit library accidentally linked into the 64-bit build. Wait for more stable build.
The red border around the active view disappeared. It happened at the same time as the rendering problems. Bug 4171.
Dean has a feature request very important to him: the ability to select and cull an Exodus part by selecting it with the mouse. Dean visualizes Exodus data with, literally, hundreds of blocks. He has little notion of which blocks correspond to the parts on the screen. This feature could mean the difference between him using ParaView and him using something else. Bug 4169. Deferred to ParaView 3.2.
Selecting cells did not fill the element inspector. I cannot replicate this problem on my Windows desktop. Wait for a more stable build.
There needs to be a way to add annotation that gives the current time. Bug 3058.
The "Save Screenshot" function failed to make a valid .jpg or .png (or at least, one that can be read by xv). It works fine on my Windows desktop (when read back in with IrfanView). Works for me now. Wait for a more stable build.
When "Save Screenshot" finally did save a valid image (to a .bmp file), it captured the file browser dialog box. Seems to work for the moment. Releated to Bug 3924
The block selection widget is not very friendly when trying to select a contiguous range of blocks (that is, do a shift click). Bug 4173
It is not evident what the "visible" option means for 3D widgets. Bug 4174
When a new filter is created, the new data does not have the same coloring as the input data. Bug 3864
The threshold filter does not turn off the visibility of its input. Bug 3896

Mike Wong