Re: Why thread limitations on mouse reads?

*bump* as this is an important issue.  You're cutting out a lot of
opportunity with this unecessary restriction.

Also, what about trap restrictions that were going to go such as on
width/height/shrink/hshrink/vshrink?

On Wed, 2004-04-07 at 06:56 +0000, Charles Goodwin wrote:
> 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

-- 
- Charlie

Charles Goodwin <[email protected]>
Online @ http://www.charlietech.com