When the mouse button is clicked on the up or down buttons of a spin-button,
it calls "arrangeForFirstDing", which forks process which does a 300ms delay
then runs "dingController" - which can get into "accept" which then
kicks the
"model" -- from this forked process.
Its only a problem if something holds up the spin value change for
300ms, which
my code does in some cases, and if you try and debug it it certainly does.
Seems to me that this (and #arrangeForFutureDing) both need to use
"uiEventFor:"
if it can find the window, and if the window it finds is nil just skip
the whole thing.
Nasty to kick UI things from two processes :(
--
Dennis Smith +1 416.798.7948
Cherniak Software Development Corporation Fax: +1 416.798.0948
509-2001 Sheppard Avenue East
[hidden email]
Toronto, ON M2J 4Z8 sip:
[hidden email]
Canada
http://www.CherniakSoftware.comEntrance off Yorkland Blvd south of Sheppard Ave east of the DVPTher
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
