John,<br><br>What are describing is not a bug at all. And even if you set the GUI size explicitly before saving the image you will indeed get exactly the same effect. Here's the reason: all 3D actors in the scene as positioned using 3D world coordinates, however all 2D entities such as scalar bar, orientation axes etc. are position using display coordinates. So whenever you change the aspect ratio as dramatically as you are, you can expect considerable placement changes with legends and such. For fun, setup the paraview gui and then resize the paraview windows to mimic the aspect ratios you are using and you shall see that the GUI behaves no differently.<br>
<br>Utkarsh<br><br><div class="gmail_quote">On Mon, May 11, 2009 at 7:25 PM, John <span dir="ltr"><<a href="mailto:bitumen.surfer@gmail.com">bitumen.surfer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Utkarsh,<br>
<br>
I did attempt to attach images to my original response. (as my wording
indicated) - perhaps because of their nature and it being a mailing
list they were pruned ? (for this reason I dropped the list from this
email) <br>
<br>
Anyway - have attached three images to this email to illustrate.<br>
a) the first ("as_displayed.png"): I made no changes to the resolution
when I saved this (760x620) so this is what I see on my screen layout.
Call it the reference image (it's purely created for the purpose of
displaying this issue - had to omit large sections of my image for
proprietary reasons)<br>
b) "height_200.png" - ok, same screen layout. The only change is that
during the "save screenshot" process I used a vertical resolution of
200 (instead of 620). The resultant image has the dummy shrunk - but
the legend has not changed scale (and actually obscures the foot
slightly). Also the axes indicator has scaled down.<br>
c) "width_1000.png" - same scenario as before, except this time I
exported as a width of 1000 (versus 760 originally). In this image the
axes indicator has not scaled visibly (but it did with a vertical
change in resolution). Also the legend has increased in size (width and
height - to maintain aspect ratio I suspect) - text size has also
increased. <br>
<br>
The resultant issue is that some elements of an image behave
differently depending on the chosen resolution - if I can't see (&
specify) the resolution on my screen as I compose the image how do I
know exactly what I will get when I save the screenshot. It is arising
from the issue of repeatability - as numerical simulations conclude I
want to be able to bring up the same viewing , angle, zoom, etc, as a
previous image. However as my screen layout may have changed I was
wanting to be able to specify the size of it (or failing that, be able
to easily see its size so as to drag manually to that desired).
Lookmarks don't work as the underlying dataset and elements may
actually changed (different surfaces/filters, etc) <br>
<br>
In regard to setting the sizes, I'd only listed the options I'd
found/played with - hadn't actually used the "Info" variants to set the
size. Couldn't understand why a unique variant required as it was
possible to obtain information from non "Info" name. Thanks for the
heads up.<br>
<br>
Cheers,<br><font color="#888888">
<br>
John</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
Utkarsh Ayachit wrote:
<blockquote type="cite">John,<br>
<br>
The "Info" properties are information-only properties which are used to
get information about certain ivars from the server. These should never
be set by the client/python script. These are managed by ParaView
server manager.<br>
<br>
As far as specifying GUI size goes, you have set both GUISize and
ViewSize; GUISize is the size of the entire view including all views in
a multiview layout while view size is the size of each individual view.
However it's not recommended to use these properties through the python
shell in the GUI. (It's totally valid to use them in pvpython or
pvbatch). Reason being the GUI is free to change them whenever it feel
like to ensure that layout is correct. <br>
<br>
You say there are issues with legend which depend on actual GUI size,
which is why you are not using the save image with resolution API. Can
you attach a screenshot with the issue you are referring to?<br>
<br>
The axes indicators cannot be moved through python. You have to use
"View Settings" (Edit|View Settings) for that.<br>
<br>
Utkarsh<br>
<br>
<div class="gmail_quote">On Sun, May 10, 2009 at 10:01 PM, John <span dir="ltr"><<a href="mailto:bitumen.surfer@gmail.com" target="_blank">bitumen.surfer@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Hi David,<br>
<br>
David Doria wrote:
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">
<div>On Thu, May 7, 2009 at 1:28 AM, John <span dir="ltr"><<a href="mailto:bitumen.surfer@gmail.com" target="_blank">bitumen.surfer@gmail.com</a>></span>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
However, I have one difficulty, if I have exited paraview or resized the<br>
windows (or .#%#@.. it crashed ) the size & aspect ratio of the
window<br>
displaying my 3D view may change. This results in my screenshots have<br>
differing resolutions i.e. my first series had 1198x712 but my next was<br>
1106x780. I know you can specify this resolution in the save screenshot<br>
dialog - however this is after the fact and some elements seem to differ<br>
based on the real size (i.e. legends)<br>
<br>
I can't seem to find an option to specify the size of this window, but I<br>
assume I may be able to via python ? can anyone help with this ?<br>
<br>
Also would love to know how to move the location of the orientation
axes ?<br>
<br>
<br>
</div>
_______________________________________________<br>
</blockquote>
<div>
<div><br>
<br>
Is it view.ViewSize you are looking for?<br>
<a href="http://www.paraview.org/Wiki/ParaView/Python_Scripting#Take_a_Screenshot_of_a_VTP_File" target="_blank">http://www.paraview.org/Wiki/ParaView/Python_Scripting#Take_a_Screenshot_of_a_VTP_File</a><br>
That is in my "outside paraview" area, which means I've only tried it
from a terminal, running the script with<br>
pvpython ./script.py<br>
<br>
</div>
</div>
</div>
</blockquote>
Actually this page was part of my inspiration in writing my original
script (thanks BTW if you are responsible for this page). I guess I was
after the ability to change my GUI window to match what would be
produced at the 'save screenshot' stage. In part because we are not
overly automating each image and in general might be making tweaks to
each image of a set. We also wanted to avoid going to another program
(i.e. gimp) to clip/resize our image. <br>
As we are not graphical experts (scientists/engineers) we are learning
some of this on the fly. <br>
Our approach in the past has been to compose our image (w.r.t. to axes
indicators, legends, etc) based on what we can see. In this respect we
are used to setting our window size (perhaps scaled to fit display
constraints) and placing our objects on this canvas. <br>
<br>
Additionally, if the resolution we specify at 'save screenshot' stage
is different to what we can see in the GUI some elements do change.
I've attached two images to illustrate.<br>
One is when we simply saved with no change to the resolution (760x620)
the other when we changed the width to 1000 (in the save GUI) and saved
(because this may match a previous image resolution to which we will
compare with). What happens is that some image elements are dependent,
such as the legend in this case. (& axes indicators also - but this
seems to only apply to height scaling from what I've seen - bug ?)
Actually - I've attached 3 images - all produced from same GUI window,
but with different export resolutions.<br>
<br>
It was for this reason we wanted to be able to specify the GUI window
size. I've tried it, but with limited luck as I don't know how to (or
which) object controls the GUI.<br>
I've tried setting these:<br>
view.ViewSize=[900,700]<br>
view.RenderWindowSizeInfo=[900,700]<br>
view.RenderWindowSize=[900,700]<br>
view.GUISize=[900,700]<br>
<br>
Separate queries:<br>
1) what is the significance of the "Info" variants? 4 or 5 properties
seem to have a duplicate with only "Info" tacked onto the end of the
name.<br>
2) Anyone know how to move/specify the location of the axes indicators ?<br>
<br>
Cheers,<br>
John<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br>