From: Jim I. <ji...@ap...> - 2002-09-03 17:17:02
|
I will look at this some more today. I got a sample timer script from=20= James Hopper that wasn't updating for him till he moved the mouse. =20 Unfortunately, it works fines for me. I saw it mess up just once, and=20= then I moved the mouse around a bit and it got fine again. However, I would believe there are some Jaguar changes to events that=20 are messing us up. I noticed that Scrollbars weren't updating at all=20 in Jaguar, and it was because dragging in a scrollbar now delivers=20 kEventMouseDragged, not kEventMouseMoved as it did in Puma. Sigh... I=20= fixed that one. I also wonder if we are getting something wrong in=20 foreground-backgrounding the App. I figured out what the event a Dock=20= click sends (kReOpenApplication or something like that). According to=20= the docs, you should just call SetFrontProcess on yourself, and that=20 will bring all your windows to the foreground. But it doesn't do that=20= for Wish. Humm, something is fishy somewhere. I think one good thing to try is=20 just to insert the standard Carbon Window Event handler back into the=20 event handling chain. We took it out because it was causing problems=20 when we tried to have the Carbon events handled on a worker thread, but=20= it might work on the main thread. Then we might get the magic right=20 setup when windows are activated??? Anyway, if anyone has any other small test cases that fail reliably for=20= them, send 'em on. Jim On Tuesday, September 3, 2002, at 07:06 AM, Daniel A. Steffen wrote: > Fran=E7ois, > > On Tuesday, Sep 3, 2002, at 23:41 Australia/Sydney, Fran=E7ois B=E9rard=20= > wrote: > >> I'm using aqua-tk on Mac OS X 10.2, built from the cvs-sources with=20= >> the last developper tools (august update). > > great, good to hear that others managed to get the build working. > As soon as 8.4.0 final is tagged I'll check in some small project=20 > updates that didn't make it in for the release. > >> The problem I have is the following: the application looks frozen=20= >> until I move the mouse. This is true for the tk windows as well as=20 >> the console. When the mouse stops, the application looks frozen=20 >> again. The keyboard buffer seems to be always alive: I can type stuff=20= >> when the application is frozen, all this stuff will appear the next=20= >> time I move the mouse. > > Yes, this seems to be a new bug with Jaguar, essentially events are=20 > not processed until the mouse is moved/clicked. > > the problem is in tclMacOSXNotify.c (DoActualWait) where > ReceiveNextEvent(0, NULL, waitTime, false, &eventRef); > hangs until a mouse event occurs, for some reason. > > Looking into it currently, but it doesn't appear simple... > > Cheers, > > Daniel > > -- > ** Daniel A. Steffen ** "And now to something completely > ** Dept. of Mathematics ** different" Monty Python > ** Macquarie University ** <mailto:st...@ma...> > ** NSW 2109 Australia ** <http://www.maths.mq.edu.au/~steffen/> > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390 > _______________________________________________ > Tcl-mac mailing list > Tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac > -- Jim Ingham ji...@ap... Developer Tools - gdb Apple Computer |