Skip to content
GitLab
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,960
    • Issues 1,960
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 96
    • Merge requests 96
  • 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

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #17843
Closed
Open
Issue created Nov 20, 2017 by Utkarsh Ayachit@utkarsh.ayachit⛰Contributor

Mismatch in generated image size with Save Screenshot

On occasion, ParaView fails to generate an output image matching the requested size. Simply run the script as follows:

# Using ParaView 5.4.1 on Linux
> pvpython -dr foo.py

Instead of generating a 300x300 image, it generates a 300x299 image.

The issue arises because the vertical layout size in the file is odd and then when it splits that into two parts, the math in vtkSMViewLayoutProxy::SetSize has rounding issues and looses 1 pixel from the requested size.

Edited Nov 20, 2017 by Utkarsh Ayachit
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking