From: Bartosz <ba...@mi...> - 2004-08-12 16:42:09
|
Thanks for your quick response, If I understand You correctly, I should, in a way, wrap my whole wxPython Application in a non visible PythonCard App, but it brings me to another question : How do I start my wxPython App as a child window of PythonCardApp ? Thanks again for your help (and for PythonCard in general :) -- Bartek Wilczynski Citing Kevin Altis <al...@se...>: > I don't think you're going to be able to do this without some clunky > workaround. If you created a background that isn't visible as your main > PythonCard window and started as a PythonCard app, then your wxPython > window could be set to be your main top level window and it would look > just the same as if you started as a wxPython app. When you need to > create your PythonCard child window you can call child window using the > hidden window as the parent then store a reference to the child in your > wxPython window as well. > > There is a lot of initialization that is done for PythonCard when the > application is created, so without having a base PythonCard app a lot > of variables just don't exist. The childWindow function itself is very > simple, so you could do your own version to work around the parent > problem. > > ka > On Aug 11, 2004, at 11:55 PM, Bartosz Wilczy¨˝ski wrote: |