Am Donnerstag, 30. Dezember 2010, 22:34:20 schrieb Giovanni Bajo: > 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?
As long it is set to 1 in the plist it complains about paythonw. It goes away when setting it to 0 > > > 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? I am not sure what is meant by double bouncing icon. I see a bouncing icon coming up and vanishing after a few seconds not matter if I set 1 or 0. It never saw a change by changing myAppName to MacOS/myAppname Let me know what you want me to try. > If so, then we should go this way and remove > this LSBackgroundOnly hack altogether! -- 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.
