QTR-Quadtone RIP

Again, thanks for the fast reply.

I just did some testing.  This is repeatable every time.  If Auto-
Orient is checked in the options menu then the image will auto-rotate 
every time when the "Print" button pressed.  So if the image rotates 
on load and then I override the orientation selected by QTRgui, 
QTRgui will then auto-orient the image again when Print is pressed.

Whether you consider this a bug or not I don't know.  But as long as 
I know how it operates I can deal with it.

Mike

--- In QuadtoneRIP@yahoogroups.com, "Stephen Billard" <stephen@...> 
wrote:
>
> The auto rotation happens only when the picture is loaded or the 
AutoOrient
> option is checked.
> 
> Other things that could (somehow) be happening:
> 
> The Portrait/Landscape radio box is getting clicked.
> The picture is dragged and dropped without your noticing.
> 
> There is NO orientation done at printing time. AutoOrient would 
never rotate the
> picture to the wrong aspect.
> 
> -Stephen
>  www.sbillard.org/Stephen
> 
> -----Original Message-----
> From: QuadtoneRIP@yahoogroups.com 
[mailto:QuadtoneRIP@yahoogroups.com] On Behalf
> Of Mike Dawson
> Sent: Saturday, February 03, 2007 5:11 PM
> To: QuadtoneRIP@yahoogroups.com
> Subject: [QuadtoneRIP] Re: QTRgui - Forced landscape rotation
> 
> Stephen,
> 
> Thanks for the reply.  It sounds like you're saying that you don't 
know why
> QTRgui would start doing this.  I know about the auto-rotate option 
(which I
> usually have selected).  This was definitely not happening when I 
loaded the
> image.  It was happening when I pressed the "Print" button.
> 
> Let me ask you this.  The one picture I was trying to print was 
square but
> perhaps 0.1" inch wider than taller.  The other image that did this 
was the ink
> separation calibration image, which is wider than taller.  The 
calibration page
> would load in landscape orientation as expected.  I would then 
change the
> orientation to portrait.
> 
> Do you think this could be the issue?  You say auto-rotation is not 
supposed to
> happen at print time.  But maybe that is what is actually 
happening???
> 
> Mike
>