On startup, the editor of the Windows version (both 3.6 and 3.7)
automatically reloads all files that were open in the previous session.
Is there a setting to prevent this?

It's mostly a problem with keep single instance when opening files
from explorer, this ends up with a lot of files being open in two
instances and me always editing the unintended version ;)

I think the reloading should normally not occur when an explicit
file name is passed as command line parameter. Actually I'm not sure
if 3.6 did this, couldn't get Windows to restore the file association
to the old binary (I think it got confused because the name of the
exe is identical).

Post a reply to this message

On 8/12/2012 15:10, Christian Froeschlin wrote:
> On startup, the editor of the Windows version (both 3.6 and 3.7)
> automatically reloads all files that were open in the previous session.
> Is there a setting to prevent this?

You can supply /norestore on the command-line if you wish.

-- Chris

Post a reply to this message

Chris Cason wrote:

> You can supply /norestore on the command-line if you wish.

ah, perfect and vaguely familiar too ;) I think I changed
the shell commands for 3.6 years ago, so I first thought the
behavior was changed with 3.7, when in fact it was just the
file association that got updated by the 3.7 installer.

BTW I encountered a strange effect:

   /NORESTORE /EDIT xyz.pov

worked, but

   /EDIT /NORESTORE xyz.pov

appeared to be interpreted as /RENDER instead.

Post a reply to this message

Christian Froeschlin wrote:
>
> BTW I encountered a strange effect:
>
>    /NORESTORE /EDIT xyz.pov
>
> worked, but
>
>    /EDIT /NORESTORE xyz.pov
>
> appeared to be interpreted as /RENDER instead.

Wild guess: would /EDIT xyz.pov /NORESTORE work better?

-Aero

Post a reply to this message

Eero Ahonen wrote:

> Wild guess: would /EDIT xyz.pov /NORESTORE work better?

I see what you're getting at ;) yes that works too.

Post a reply to this message