[Pythonmac-SIG] Re: Carbon Tkinter/Python 2.2

[Jack Jansen]

On Friday, January 25, 2002, at 07:14  PM, Christopher Smith wrote:
> ==> If I click the mouse first, the cursor does not appear until the
> second click. I can successfully navigate between text boxes 
> but when the
> mouse gets down in the check box region, it disappears but 
> remains active
> (so I can blindly click on the check boxes even though I can't see the
> cursor).  I can get the "event delayed" behavior that Jack noted by
> clicking on the desktop first AND THEN clicking in the console.

There's a good chance I got into this mode through similar 
means, or maybe through selecting the Apple menu first or 
something.

Everything we've seen so far, even though the symptoms are 
pretty different in different circumstances, seems to point to a 
problem with WaitNextEvent(). Now, in CarbonLib WaitNextEvent() 
is really a simulated call implemented with Carbon Events, i.e. 
the lowlevel mechanism is Carbon Events.

So in the one process part of the code (Python's cmd-. handler, 
GUSI's wait spinloop) uses the Carbon simulated WNE and another 
part of the code (Tk) uses the real old-style WNE in 
InterfaceLib. It could be that this leads to the strange 
behaviour we see.

Does anyone here know whether this hunch is worth pursuing? Any 
idea where we could find more info on this?
--
- Jack Jansen        <Jack.Jansen@oratrix.com>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -