From: Kevin A. <al...@se...> - 2004-08-12 15:44:42
|
I don't think you're going to be able to do this without some clunky=20 workaround. If you created a background that isn't visible as your main=20= PythonCard window and started as a PythonCard app, then your wxPython=20 window could be set to be your main top level window and it would look=20= just the same as if you started as a wxPython app. When you need to=20 create your PythonCard child window you can call child window using the=20= hidden window as the parent then store a reference to the child in your=20= wxPython window as well. There is a lot of initialization that is done for PythonCard when the=20 application is created, so without having a base PythonCard app a lot=20 of variables just don't exist. The childWindow function itself is very=20= simple, so you could do your own version to work around the parent=20 problem. ka On Aug 11, 2004, at 11:55 PM, Bartosz Wilczy=A8=BDski wrote: > Hi, > > I'm trying to embed Pythoncard in an existing wxPython Application.=20 > What I want > to do is to open a pythoncard background as a child window of my=20 > wxpython app. > > The problem I have is that I can either try to use > > model.childWindow(wxApp,someClass) > > - but it does not work as wxApp has no stack > > model.PythonCardApp(someClass) > > - which does the wxApp initialization again and breaks everything. > > There should be at least one (and preferably only one) elegant method=20= > to do it. > > Anyone has any ideas ? > > Thanks for any help in advance > -- > Bartek Wilczynski |