I'd appreciate 2 words here, as my post was badly timed right after RC6,
and I hate to wait 1 month for the next release to find out if my report
made any sense to anyone, while everybody is involved in an endless
(=infinite) dance around the hat operator (apologies to mexican readers,
no offense intended). In case I failed to make myself clear enough,
here's how to reproduce. It assumes you have both Win POV 3.1g and 3.5
(any beta/RC) installed and for no particular reason you need to have
them running at the same time (quite common case during beta testing, I
guess).

1. Launch 3.5 only to check menu "Options/Keep Single Instance" and also
"Options/Other Settings/Save Settings on Exit" (or make sure they're
checked). Now close 3.5.
2. Launch 3.1g and leave it running (visible, minimized, in the system
tray, whatever).
3. Now TRY to launch 3.5 in any manner (startup menu, shortcut, click
pvengine.exe, click .pov file) and observe how each time 3.5 thinks 3.1
app is its own instance, so walks away. See? Told you so :)

Of course, you could launch 3.5 first, but then again 3.1 may have been
set itself to keep single instance. Am I the only one who sees this
behaviour as abnormal? I wrote so much about so little because to SEE
the problem is really the hardest part here, fixing (read original msg)
is piece of cake.

Thx,
G.

"Gelu Stoicescu" <gel### [at] homero> wrote in message
news:3d03bd09@news.povray.org...
| Win POV
| 3.5.beta.RC5.icl.win32
| 3.1g.watcom.win32 [Pentium IIoptimized]
| OS Win98 SE, hardware not an issue
| (nothing improved since my last post, sigh...)
|
| Problem:
| When either one of versions 3.1 or 3.5 (RC5 for that matter) is
| "running" and the "other version" is set to run single instance, when
| launching the "other version" it inadvertedly recognizes the "running"
| instance as its own and brings focus on the existing window instead of
| launching itself. <...>

Post a reply to this message