raffaello wrote:
Must have missed something, because both theFile and PyCrust start, but quite on separate rails.
Huh? What do you mean? What do you expect?
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
raffaello wrote:
What happens is that the window of PyCrust opens, and the same does the window of the «wrapped» file, e.g. spare.py, but on its own, not inside PyCrust, exactly as if I had clicked in Explorer the names of the two files.
What I expected was to see spare.py «inside» PyCrust, to read, analyze and maybe debug it: therefore I said that I must have missed or misunderstood something.
PyWrap is not that kind of wrapper. It simply adds an instance of the PyCrust frame and shows it in addition to your app. So they are both running in the same process, but it doesn't try to embed your app in the same window. If you look at the output of dir() in the PyCrust shell you'll see that there is an 'app' variable which is a reference to your app object, so you can use that to get access to the various attributes of the app being examined.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!