MantisBT - ParaView
View Issue Details
0007607ParaView(No Category)public2008-09-04 15:122009-05-13 13:47
Alan Scott 
Utkarsh Ayachit 
normalminoralways
closedunable to reproduce 
 
3.6 
0007607: LOD Apply button, selections do not work
I believe that the LOD selections Apply button does not work. This includes the LOD Resolution and Outline Threshold buttons.

Run ParaView client/server (6 servers), open can.exo.
Edit/ Options/ Render View/ General.
Turn LOD Threshold on (select box), slide to 0.0 MBytes.

Bug >> Slide the LOD Resolution slider back and forth, hitting Apply button. Nothing happens. Slide the LOD Resolution slider back and forth, hitting OK. It seems to work.

Bug >> Slide the outline Threshold to 0 MCells, hit OK. Can still doesn't go to threshold representation.
No tags attached.
Issue History
2008-09-04 15:12Alan ScottNew Issue
2008-09-16 16:11Utkarsh AyachitStatusbacklog => @80@
2008-09-16 16:11Utkarsh AyachitResolutionopen => unable to reproduce
2008-09-16 16:11Utkarsh AyachitAssigned To => Utkarsh Ayachit
2008-09-16 16:11Utkarsh AyachitNote Added: 0013482
2008-09-17 15:51Alan ScottStatus@80@ => closed
2008-09-17 15:51Alan ScottNote Added: 0013490
2009-05-13 13:47Utkarsh AyachitTarget Version => 3.6
2011-06-16 13:10Zack GalbreathCategory => (No Category)

Notes
(0013482)
Utkarsh Ayachit   
2008-09-16 16:11   
Bug 1>> Create a sphere with theta and phi resolution = 100. Change representation to wireframe. Now change the LOD resolution, hit apply and the interact. With CVS head, I see that the wireframe simplification changes with the LOD resolution as expected.

Bug 2>> Outline Threhold is the only used when creating the representation (not when some data is already shown). So after chaning the threshold to 0, and existsing can.ex2 won't go to outline mode. However, if you load a new can.ex2 then it will show up as outline by default. The user can still change it to surface or whatever representation he chooses.
(0013490)
Alan Scott   
2008-09-17 15:51   
first bug appears to have been fixed.
Second bug appears to be user error.

Tested client/server.

Closed.