The problem is that if you run 2 wxPython scripts, they should run *as
separate applications with separate menubars*.
If menubars are associated within a window-- not the Macintosh way and a
probably less effecient means of presenting a menubar-- as it is on
Windows and most X11 environments, then it isn't an issue.
With a true menubar, it is an issue.
Furthermore, they really want to run in separate interpreted processes as
that ensures that if one instance of Python.app dies, it doesn't take out
all wx* based applications.
On Wednesday, March 27, 2002, at 11:43 AM, Jack Jansen wrote:
As a sideline, I don't understand the bit about "So for example, when a
wxPython script is executed, the Mac OS sees any windows the script
creates, or menus it tries to create, as belonging to Python.app - not to
that particular script.". This is also something I've heard here before,
and I don't understand how it could be otherwise. X11 also sees windows
as belonging to a process (or actually a socket connection, in it's case)
. MS-Windows too. Any other window system I'm aware of as well. The
script isn't an entity the window server will know about, it's just
processes (and/or connections).
b.bum
I ride tandem with the random....
.... things don't run the way I planned them.
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
