From: Tony L. <to...@me...> - 2001-12-06 22:55:07
|
> >SUGGESTED CHANGE TO tkMacOSXInit.c:TkpInit() >When a Ruby script that uses Tk starts up, it calls the following >Tcl/Tk functions to get started: > Tcl_FindExecutable > Tcl_CreateInterp > Tcl_Init > Tk_Init >What I noticed is that there are some very important looking >functions that only get called from tkMacOSXAppInit.c:main() or >tkMacOSXAppInit.c:Tcl_AppInit(). Specifically, they are >tk_MacOSXSetupTkNotifier(), TkMacOSXInitAppleEvents(interp), and >TkMacOSXInitMenus(interp). I just got Python/TkAqua (Tkinter) to work. What I did was to put those TkMacOSX* calls in the Tkinter code directly. What stumped me was that TkMacOSXSetupTkNotifier must be called early, which is clearly documented; so I made sure it happened before Tcl_CreateInterp. Actually, it must be called before Tcl_FindExecutable as well. >SO WHERE DOES THAT LEAVE ME ? >Well, acutally, not much better off :-( I can now guarantee that my >event loop is running which is a Good Thing (TM). However, I still >only see the window appear when I run under gdb. And when I click on >the window I get a new message about SetFrontProcess failing with an >error code of "-600". I think this means your executable is not a .app bundle when, to be a gui program, it must be. -Tony -- |