Re: Why thread limitations on mouse reads?
Adam Megacz <[email protected]> Sat, 10 Apr 2004 00:17:51 -0700
| Newsgroups | gmane.comp.java.xwt.core |
|---|---|
| Organization | XWT |
| Message-ID | <[email protected]> |
The limitations are there so that some boxes can fake mouse actions from the perspective of other boxes. If a box can look at the mouse at any random time, it's going to be really hard to fake it. The real solution (which I haven't gotten around to implementing yet) is to have Press1, Release1, Move, etc put an (x,y) mouse position instead of 'true'. - a Charles Goodwin <[email protected]> writes: > If I have a thread that passes a value to a property who in turn makes > use of a call to box.mouseinside, box.mouse.x, or box.mouse.y, the > follwing error is given: > > Scheduler: a JavaScript thread spawned with ibex.thread() > threw an exception: > at > file:src/org/ibex/theme/win2k/scrollbar.t:36 > at trap on property "action" > at file:src/ibex/lib/repeatable.t:30 > JSExn: you cannot read from the box.mouse property > in background thread context > at org.ibex.Box.get(Box.java:523) > at > org.ibex.js.Interpreter.run(Interpreter.java:313) > at > org.ibex.js.Interpreter.resume(Interpreter.java:39) > at org.ibex.js.JSFunction.perform(JSFunction.java:31) > at > org.ibex.Scheduler.defaultRun(Scheduler.java:77) > at org.ibex.Scheduler.run(Scheduler.java:54) > at org.ibex.Scheduler.init(Scheduler.java:17) > at org.ibex.Main.main(Main.java:101) > > This seems like a very unecessary limitation and rules about basically > any time-based interaction with the mouse. > -- > - Charlie > > Charles Goodwin <[email protected]> > Online @ http://www.charlietech.com > > > _______________________________________________ > core mailing list > [email protected] > http://lists.xwt.org/listinfo/core > -- "It's lucky," he added, after a pause, "that there are such a lot of islands in the world. I almost envy you, Mr. Watson." -- Mustapha Mond