Hi, don't knwo if this has been hashed to death already...
On the Mac, the cmd-R and cmd-I shortcuts (start rendering and edit info) don't work
when the preview window is frontmost. This is somewhat inconvenient especially
when I want to re-render selected areas of an image with slightly different
quality parameters, because I won't touch the editor window in this case.

Cheers,
Hans-Martin

Post a reply to this message

In article <3CD### [at] heegde> , Hans-Martin <hmm### [at] heegde>  wrote:

> On the Mac, the cmd-R and cmd-I shortcuts (start rendering and edit info)
don't work
> when the preview window is frontmost.

This is because the preview window is not dependent on the scene but only on
the current render.  That is, you can close the scene while rendering is in
progress.  Among other things this allows to have multiple preview windows for
multiple scenes without having those scenes in memory.  Having multiple
preview windows for the same scene is possible as well also there isn't
current any user-controllable way to do activate this feature.

I agree this isn't ideal, but so far no good solution to keep both features
has been found.

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:

> I agree this isn't ideal, but so far no good solution to keep both features
> has been found.


I agree too that the current behaviour is a little bit frustrating,
compared with the perfect 3.1g behaviour.

There might be some workarounds, however, for the very common situation
where the scene rendered in the current preview window is still in
another window. 

Why not just keep a pointer to the scene file in the preview window (or
maybe just a string containing the name of the scene file); then when
the user hits cmd-R or cmd-I while a preview window is frontmost, check
if the scene is still in memory, in which case you can bring the
appropriate dialog window(s) for quality settings, etc...


Hope this simple idea helps :-)
Stephane.

Post a reply to this message

Nicolet) wrote:

> Why not just keep a pointer to the scene file in the preview window (or
> maybe just a string containing the name of the scene file);

Oh, come on.  You really think I could just put some pointer somewhere and
would not have such an ideal myself?  Please...

    Thorsten

Post a reply to this message

> Thorsten Froehlich <tho### [at] trfde> wrote:
> 
> 
>>I agree this isn't ideal, but so far no good solution to keep both feat
ures
>>has been found.
> 
> 
> 
> I agree too that the current behaviour is a little bit frustrating,
> compared with the perfect 3.1g behaviour.
Well I would not call 3.1g behavior perfect!
I'd rather have multiple open files than the shortcut keys on preview win
dows :-)

> Why not just keep a pointer to the scene file in the preview window (or

> maybe just a string containing the name of the scene file); then when
> the user hits cmd-R or cmd-I while a preview window is frontmost, check

> if the scene is still in memory, in which case you can bring the
> appropriate dialog window(s) for quality settings, etc...
> 
Yup, I'd think that would be a good solution.
> 
> Hope this simple idea helps :-)
> Stephane.

Cheers,
Hans-Martin

Post a reply to this message