Sorry for my late reply, I have been a bit too busy lately...
At 23:44 01.05.2002 +0200, you wrote:
>On Wed, 01 May 2002 23:35:10 +0200 Matthias Baas <[EMAIL PROTECTED]> wrote:
>
>MB> I tried it, but it didn't change anything, the program still refuses to
>MB> start up.
>
> It's really incredible that the debug version simply disappears like this.
>If it crashed, we could debug it further but if there is really nothing
>that happens I don't know what else to do :-( Maybe you could try to run it
>under regmon and/or filemon (see www.sysinternals.com) to see what is it
>doing?
Thanks for this link, these tools are most interesting!
However, I'm a bit overwhelmed of the flood of information I get. What
exactly is it I have to look for?
BTW, meanwhile I believe it's actually wxWindows that's causing the
problem. Recently I installed wxPython to have another look at the
wxWindows toolkit. And all the sample programs also show the same
(mis)behaviour as Mahogany, they just don't start up. For example, I tried
the following demo from the tutorial:
from wxPython.wx import *
class MyApp(wxApp):
def OnInit(self):
frame = wxFrame(NULL, -1, "Hello from wxPython")
frame.Show(true)
self.SetTopWindow(frame)
return true
app = MyApp(0)
app.MainLoop()
And here, it's the first line in OnInit() where the wxFrame is created that
silently kills the program.
Maybe this demo program and Mahogany don't start up for the same reason.....
- Matthias -
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Mahogany-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-users
