On mar, 2010-12-28 at 15:57 -0500, Concussion GFX - Tim wrote: > The pythonw error is due to the "LSBackgroundOnly" being set to 1 > (True) in the plist. If you remove this from the plist then you app > should launch.
We lately changed the bootloader so that the background flag of the process is reset to 0 (at the kernel level) before Python code gets a change to get executed. Is this still a problem? > I use the -onefile option. So the workaround above causes 2 icons to > be present after launch. To fix this I need to add "MacOS/" to the > "Executable file" entry in the plist. so the final entry looks like > "MacOS/myAppName" So if you use "MacOS/myAppName", there is no double bouncing icon even with LSBackgroundOnly=0? If so, then we should go this way and remove this LSBackgroundOnly hack altogether! -- Giovanni Bajo :: Develer S.r.l. [email protected] :: http://www.develer.com Blog: http://giovanni.bajo.it Last post: Compile-time Function Execution in D -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
