MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009489ParaViewFeaturepublic2009-09-04 10:182016-08-12 09:57
ReporterDavid Doria 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0009489: Automatically adjust point/line sizes for screenshots with different resolution
DescriptionIf you have points or lines in the scene and you take a screen shot at a higher resolution than the current window (say 5000x5000), many of the objects stay the same size (spheres, planes, triangulated meshes) but many objects get much smaller (points, lines). Surely this is because the points and lines are specified in arbitrary units (Point Size = 3, Line Width=2, for example). An example is here:
http://rpi.edu/~doriad/Paraview_List/linesize.jpg [^]

Notice the lines in the screenshot are much thinner.

It would be nice to have theses sizes automatically adjusted to the relative difference between the screenshot size and the render window size, so screenshots will look the same.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-09-04 10:18David DoriaNew Issue
2010-02-12 11:57David DoriaNote Added: 0019516
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature
2016-08-12 09:57Kitware RobotNote Added: 0037697
2016-08-12 09:57Kitware RobotStatusexpired => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved
2016-08-12 09:57Kitware RobotAssigned To => Kitware Robot

Notes
(0019516)
David Doria   
2010-02-12 11:57   
A fix is to use vtkTubeFilter on lines and glyph spheres on points. Then everything scales as expected (and typically looks better, too).

However, it still seems reasonable for the points and lines to themselves be scaled for larger screenshots.
(0037697)
Kitware Robot   
2016-08-12 09:57   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.