View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002898Slicer4Core: Base Codepublic2013-01-29 06:052015-10-27 11:13
Reporterfinetjul Assigned Tonicole  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product VersionSlicer 4.2.2-1 
Target VersionSlicer 4.5.0-1Fixed in Version 
Summary0002898: Restore screenshot resolution for VTK render view
Description

There is currently only a post screenshot zoom factor.
For publication, it would be great to be able to generate higher resolution screenshot of 3D or 2D views.

Additional Information

This feature was working in Slicer 3

TagsNo tags attached.

Relationships

duplicate of 0003885 assignednicole Update qMRMLScreenShotDialog to support high-resolution magnified screenshot 
related to 0002895 assignednicole Screenshot dialog can't take screenshot of charts 
related to 0001472 acknowledgedjcfr Factorize ctkScreenshotDialog with qMRMLScreenshotDialog 
related to 0003858 closednicole Scale factor is broken when saving screenshots 

Activities

sankhesh

sankhesh

2013-01-29 06:17

developer   ~0007748

This feature has been added to ctkScreenshotDialog - https://github.com/commontk/CTK/commit/c7741eaca6fed809f353644f5bc2715bfba6462f

Once, the qMRMLScreenshotDialog and ctkScreenshotDialog are consolidated, it should be available in the Annotations module screenshot dialog of Slicer.
jcfr

jcfr

2013-01-29 06:27

administrator   ~0007749

See http://viewvc.slicer.org/viewvc.cgi/Slicer3/trunk/Base/GUI/Tcl/ScreenShot.tcl?view=markup
finetjul

finetjul

2013-01-29 06:44

administrator   ~0007750

What is done here:
https://github.com/commontk/CTK/commit/c7741eaca6fed809f353644f5bc2715bfba6462f

is a rescale that happens "after" the screenshot is taken. While it is satisfactory for the general usecase, such screenshots can be improved when dealing with VTK views.
Indeed, such views could temporarily generate higher resolution views with no interpolation.
jcfr

jcfr

2014-03-07 09:10

administrator   ~0011351

This would be nice to fix - but we think it's low priority right now. Let
us know if it is high priority for you or if you would like to help us by contributing a patch.
nicole

nicole

2015-10-27 11:13

administrator   ~0013435

Duplicate of 3885

Issue History

Date Modified Username Field Change
2013-01-29 06:05 finetjul New Issue
2013-01-29 06:05 finetjul Status new => assigned
2013-01-29 06:05 finetjul Assigned To => jcfr
2013-01-29 06:05 finetjul Relationship added related to 0002895
2013-01-29 06:07 jcfr Assigned To jcfr => sankhesh
2013-01-29 06:07 jcfr Target Version => Slicer 4.4.0
2013-01-29 06:09 finetjul Relationship added related to 0001472
2013-01-29 06:17 sankhesh Note Added: 0007748
2013-01-29 06:27 jcfr Note Added: 0007749
2013-01-29 06:27 jcfr Target Version Slicer 4.4.0 => Slicer 4.3.0
2013-01-29 06:44 finetjul Note Added: 0007750
2013-06-03 05:15 jcfr Assigned To sankhesh => jcfr
2013-08-19 10:03 jcfr Target Version Slicer 4.3.0 => Slicer 4.4.0
2014-03-07 09:09 jcfr Target Version Slicer 4.4.0 =>
2014-03-07 09:10 jcfr Note Added: 0011351
2014-03-07 09:10 jcfr Status assigned => acknowledged
2014-12-30 10:41 nicole Relationship added related to 0003858
2015-09-09 08:36 jcfr Status acknowledged => assigned
2015-09-09 08:36 jcfr Assigned To jcfr => nicole
2015-09-09 08:37 jcfr Target Version => Slicer 4.5.0-1
2015-09-10 07:32 nicole Relationship added duplicate of 0003885
2015-10-27 11:13 nicole Note Added: 0013435
2015-10-27 11:13 nicole Status assigned => closed
2015-10-27 11:13 nicole Resolution open => fixed