View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012153ParaViewBugpublic2011-05-04 14:162011-05-17 21:01
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.12Fixed in Version3.12 
Summary0012153: Screen often does not redraw
DescriptionWe have a new bug in ParaView, where the screen does not redraw. It can be replicated about 50% of the time as follows:

local server, trunk from May 2nd, Windows.

I believe that changing these steps can hide this bug.

paraview.exe -dr
Open can.ex2. All variables on. Apply.
Select a cell on, on the bottom of the visible plate.
Plot selection over time. Apply.

Don't touch the mouse. You will see that the 2d window looks OK, but the 3d window will go gray. Mousing in this window will then display the 3d object.

I think you see the same problem when you re-size the window. Grab the lower right corner of the ParaView window, re-size. As you are resizing, it will turn gray. This is new behavior.

I am seeing this all over the place, thus am marking it higher priority.
TagsNo tags attached.
Project
Topic Name
Type
Attached Files

 Relationships

  Notes
(0026437)
Utkarsh Ayachit (administrator)
2011-05-04 14:24

 This is new "feature" under development, so bare with it for a little as the issues are ironed out.

The goal is to avoid unnecessary re-renders whenever possible.
(0026459)
Utkarsh Ayachit (administrator)
2011-05-07 10:27
edited on: 2011-05-07 10:29

 Give it another try. I had forgotten to push a fix that ensured that the correct buffer was captured.

BTW, the grey windows while resizing is deliberate. It's a means to avoid unnecessary renders while user is resizing. This should make it easier to resize windows when the user has really large datasets being rendered that takes a whole lot of time to render.

This feature also saves on unnecessary renders as tooltips or dialogs popup over the render window.


commit 776e1a777b46a7a5ea4257c91bed549362e38a77
Merge: 6b0a51d bed6173
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Sat May 7 10:07:09 2011 -0400

    Merge topic 'minimize_renders'
    
    bed6173 QVTKWidget was capturing image from the buffer at wrong time.

commit bed617300c5459e27b091e7c4706e2f209e1887f
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Sun May 1 18:00:56 2011 -0400

    QVTKWidget was capturing image from the buffer at wrong time.
    
    SwapBuffer behaves differently on different platforms. On some it seems to paste
    contents of back buffer to front while on others it literally swaps them. The
    QVTKWidget needed to capture back buffer contents while caching to avoid issues
    with overlapped windows. So it needed an event from vtkRenderWindow that was
    fired after render was done but before swapping of the buffers. So changed
    vtkRenderWindow to fire such an event and QVTKWidget to capture the buffer on
    that event.
(0026534)
Alan Scott (manager)
2011-05-17 21:01

 I think this is fixed. I will reopen if I figure out a different way to replicate.

Tested local server, windows, trunk.

 Issue History
Date Modified Username Field Change
2011-05-04 14:16 Alan Scott New Issue
2011-05-04 14:24 Utkarsh Ayachit Note Added: 0026437
2011-05-07 10:27 Utkarsh Ayachit Note Added: 0026459
2011-05-07 10:27 Utkarsh Ayachit Status backlog => @80@
2011-05-07 10:27 Utkarsh Ayachit Fixed in Version => 3.12
2011-05-07 10:27 Utkarsh Ayachit Resolution open => fixed
2011-05-07 10:27 Utkarsh Ayachit Assigned To => Utkarsh Ayachit
2011-05-07 10:29 Utkarsh Ayachit Note Edited: 0026459
2011-05-17 21:01 Alan Scott Note Added: 0026534
2011-05-17 21:01 Alan Scott Status @80@ => closed

Copyright © 2000 - 2018 MantisBT Team