1.6.9 osx x86_64 gui behavior (and 1.6.1 actually)

[pfile]

Hi Juan -

i'm not sure if this behavior is only present on the x86_64 version of PI or not; i need to try it on the 32-bit version still. so this might fall under "graphical weirdness" on osx x86_64:

when a script is running, PI just will not stay "lowered". at some point during the execution of the script (batchformatconversion and batchdebayer both cause this), PI comes to the foreground on its own. when using OSX's spaces feature this is particularly annoying because you switch to another space while PI is working and boom, it comes right back to the space that PI is in with PI on top.

i'm still on osx 10.6.3, not sure if this has something to do with it.

[pfile]

this also happens with the 32-bit version. is it just me? it's super annoying 

[Juan Conejero]

Hi Rob,

I can't reproduce this behavior. I've tried with the BatchFormatConversion, BatchDebayer and 3DPlot scripts while I was in a different space, and the scripts terminate execution without disturbing. Could this be a configuration option or something similar? I'm not very familiar with Spaces. I have 10.6.5.

[pfile]

i'm finding that it comes and goes. i have not figured out what triggers it.

maybe can you try turning on spaces? it's just a virtual desktop manager, i'm sure you're familiar with those. it in the system preferences, top row, "expose and spaces". i have 8 spaces going (2 rows and 4 columns).

thanks

[Carlos Milovic]

This may not be a OSX only bug. When my code opened a new window, while I was on another desktop, it was changed to the one where PI was running. Fedora + KDE.

[pfile]

Hi Rob,

...while I was in a different space, and the scripts terminate execution without disturbing...

oh sorry, i can't read.

This may not be a OSX only bug. When my code opened a new window, while I was on another desktop, it was changed to the one where PI was running. Fedora + KDE.

BatchDebayer definitely creates all kinds of windows as it's running but IIRC BatchFormatConversion does not. both scripts will cause this "spontaneous raise" behavior in PI, for me at least.

[j.w.]

This actually sounds like the same thing I reported back in August (BatchDeBayer forcing PixInsight to be the active app).  Juan asked me to collect some more data, but I've been just a bit tardy in getting back to it (sorry Juan!  ).  I'm now using Mac OS X 10.6.5 and the latest versions of PixInsight for both 32 and 64 bit OS (being able to run both at the same time really helps troubleshooting by the way), and I don't see the problem anymore (runs fine in both versions).  I probably would have been on Mac OS X 10.6.4 at the time, so perhaps the upgrade is what solved the problem?

John