Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,846
    • Issues 1,846
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #18963
Closed
Open
Created Apr 23, 2019 by W. Alan Scott@wascottMaintainer

trace of multiview screenshots is bad

Traces/ Scripts of multiple view screenshots are bad. This has degraded since 5.6.0.

  • Master (v5.6.0-1312-g8ce81b84), local server, Linux.
  • Tools/ Start Trace. Just to make sure, Fully Trace Supplemental Proxies.
  • Open can.exo. Apply.
  • Split Horizontal/ Split Vertical/ Split the other (long) view Vertical. We now have a 2x2 of views.
  • Highlighting each of the gray views, turn visibility on, showing the can in each.
  • Not necessary - I clicked on +X, +Y and +Z in different views. Lower right view was just freehand.
  • File/ Save Screenshot. BE SURE to save all views.
  • Tools/ Stop Trace. Save this somewhere. Close the trace.
  • Reset Session.
  • Delete the saved screenshot.
  • View/ Python View/ Run Script. Um ... Run your script.

All 4 views don't have correct images in them! (Note that the views are now possibly out of order, depending on the order you did "Highlighting...". I will write this up as another bug.)

I also received this set of errors/ warnings:

ERROR: In / snip /ParaViewCore/ServerManager/Rendering/vtkSMViewLayoutProxy.cxx, line 596 vtkSMViewLayoutProxy (0x4a5f440): Cell is not empty.

Warning: In / snip /VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx, line 284 vtkGenericOpenGLRenderWindow (0x9d883c0): ReadPixels called before window is ready for rendering; ignoring.

Warning: In / snip /VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx, line 284 vtkGenericOpenGLRenderWindow (0x663fe10): ReadPixels called before window is ready for rendering; ignoring.

Warning: In / snip /VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx, line 284 vtkGenericOpenGLRenderWindow (0x663fe10): ReadPixels called before window is ready for rendering; ignoring.

Warning: In / snip /VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx, line 284 vtkGenericOpenGLRenderWindow (0xe285140): ReadPixels called before window is ready for rendering; ignoring.

This is a showstopper bug for the 5.7.0 release.

deleteMeM

Edited Apr 23, 2019 by W. Alan Scott
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking