* Chris Munchenberg <cjm@[...].au>  [030415 21:40]:
>  Fixed for a newbie, and karma now owes me.
Sure does, ha ha! Wow, I can't believe how helpful the people on this
list have been so far. You guys are amazing!

>  Problems:
>      Python works on indentation levels. Don't screw them up - you lose class definitions e
tc.
>      ID_EXIT wasn't defined anywhere.

I was just throwing up a quick sample to illustrate the problem and
ID_EXIT got munged out of the example in process. *sigh* Sorry about
that. Oh well, making mistakes is what being a newbie is all about...

>  Less ugly fix:
> wxGlade is great for GUI design. Do your GUI magic in another file that 
> imports and uses MyFrame. Then if you need to do GUI reworking, you don't 
> lose your GUI magic. wxGlade is pretty good at taking care of your code vs 
> its code, but I don't trust anyone else not to overwrite my code.
That sounds like a fabulous idea, but I'm scratching my head to a
polished chromedome trying to wrap my peabrain around it. So you would
keep the wxGlade generated code in say, MyGUI.py and the functions the
GUI is supposed to execute in say MyAPP.py? Then instantiate MyFrame 
in MyAPP.py or somesuch like in your DemoApp class? The events would 
still go into MyGUI I take it, but where would OnExit() go? If all the
functions go into into MyGUI.py anyway, then what's the point?

I would simply KILL for an example of this scheme. Any ideas? Or maybe I
should wait until I have gleaned through demo.py.
>  Hope this helps,

Sure did - thanks for taking the time to respond so promptly! It works
beautifully, man.
-- 
"Thinking gives you wrinkles!"
Malibu Stacy, the Simpsons

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@[...].org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org