I'd guess, from your description, that you're using agpm.py manually to 
install the app packages.  What's happening is that the shared 
application database is getting the 'wrong' python interpreter - if you 
do 'which python' on a mac, you get (after resolving soft links) 
/System/Library/Frameworks/Python.framework/Versions/2.3/bin/python, 
which, while it can start a wxPython app, has no access to the UI, so 
the GUI windows will never get focus.  If you do 'which pythonw' you get 
(after resolving soft links) a script, which executes a different 
interpreter, namely, 
/System/Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python
Only the second one (the one you get with 'pythonw') is able to actually 
run python apps with a GUI correctly.  The easy solution here is to 
always run agpm.py with pythonw instead of python (except on Linux, 
where there is no such beast).  Hope that helps ;-)

Justin Binns

Christoph Willing wrote:

> I'm trying to move some shared apps onto a Powerbook G4 (for AG retreat).
>
> These apps work well under Linux and mostly work on the G4 too. 
> However those that employ a gui are a bit strange, in that they don't 
> seem to take focus properly.This means they can't be resized or 
> dragged around the screen with the mouse. Popup menus seem to work on 
> them after a few false starts. If the gui has a menubar, it doesn't 
> appear. MessageDialogs from the gui never take focus either so they 
> never disappear because clicking the OK (Cancel etc) button never works.
>
> When these apps are started manually, they're fine and behave exactly 
> as expected. Its just when they're started by joining a shared app 
> instance via the VenueClient's "Application Sessions" node that there 
> is a problem. Its as if the VenueClient is holding onto focus, not 
> allowing its "child" gui's to take it.
>
>
> Has anyone work this out yet?
>
> chris
>
>
> Christoph Willing                        Ph: +61 7 3365 8350
> QPSF Access Grid Manager
> University of Queensland
>

Reply via email to