From: Tony L. <to...@me...> - 2001-10-19 18:42:25
|
While messing around with Tkinter, I'm having similar problems: Without adding any MacOSX specific code to Tkinter, the window Tk creates never responds to anything. I tried adding what I thought was the relevant code from tkMacOSXAppInit.c(*), and that didn't fix it... So, I tried compiling tkMacOSXAppInit.c alone to see if my problems were in how I was compiling the stuff - basically just did cc tkMacOSXAppInit.c -o a.out with a lot of -I's and -framework's And I got the same behavior! The window did not respond to events! Which leads me to wonder if I have to make a .app and not a plain binary. Jim, does that sound correct? Would the application need to be a .app? -Tony p.s. Your tk.h and tcl.h plan sounds good to me. (*) The code I added was: Tk_MacOSXSetupTkNotifier(); before Tcl_Init and TkMacOSXInitAppleEvents(v->interp); TkMacOSXInitMenus(v->interp); Tcl_CreateInterp > >On another note: >Now that I have the resulting Tk wrapper for Mozart, I attempted to >use some Mozart sample code that draws on a AquaTk canvas in a >window. >The window was created as an unselected window, and did not respond >to any mouse click by becoming selected (frontmost.) I could draw >into it with Mozart code, but the image in the Canvas did not >refresh unless I passed another window over the AquaTk window. > >The mozart code used to do a perfectly selectable window under >Tk/XFree86. (But that was under Tk 8.3, not 8.4) > >Do you think that our Mozart Tk wrapper is lacking some event >trapping code that appeared in Tk 8.4? (Does not feel likely!) >Or is it rather due to problems with the current state of the Tk >implementation? And where do you think I should go looking for those? -- |