PI 1.7.4- macosx x86 (64-bit) : window keeps raising

[pfile]

i know this has been mentioned before, and i was hoping it would be fixed with the inclusion of the new version of Qt, but it appears to have gotten worse.

whenever i execute a script, PI comes to the foreground periodically, each time a file is processed. (ex: batchformatconversion, batchchannelextraction, batchdebayer, etc.) it appears to correlate with when the "pause/stop" button on the console window undims. this behavior may only happen when using apple's virtual window manager ("spaces") since i think Juan had said before he could not reproduce it.

it used to be on 1.7.0 if i started the script and changed virtual desktops, PI would stay in the background unless i put PI back in the foreground. after that point if the script was still running, on each iteration it would raise. but on 1.7.4, it unconditionally raises itself on every script iteration.

this does not happen when an iterative process is running. it's only scripts.

this behavior renders the computer unusable until the script is finished.

[Juan Conejero]

Hi Rob,

I am still unable to reproduce this problem. I've just made another test with BatchFormatConversion and Spaces running. I can move between spaces (e.g. with Ctrl+Arrow) freely while PI is converting files. The current space is never changed spontaneously.

When the process completes, the script shows a message box "Do you want to perform another conversion?" which pops up on the current space---arguably, it should stay in the same space as PI's main window, but I know of no way to force this---and when I click a dialog button the current space is changed to show PI's main window; again, right now I can't prevent this to happen.

I'll keep trying to find a way to reproduce this behavior.

[pfile]

in my system, when i start pixinsight and then move to another space, when pixinsight starts writing to the console window with the banner and stuff, it raises itself. this is probably the same problem... does that happen on your system?

i'm trying to think of anything else i might have installed that could affect the window manager behavior...