Dear Jim
On Wednesday, December 5, 2001, at 04:02 AM, improve-revolution-
[EMAIL PROTECTED] wrote:
> I'm not sure this is the same issue, but if the sticky mouse you
> refer to is in relation to the mouse function ("the mouse" or
> mouse()), it is not a Rev problem. The source of this problem is in
> the MC engine.
>
> I pointed this problem out to Scott Raney and he replied:
>
> "See the example in the examples stack. The documentation is not
> strong enough in this case: you're on your own with "the mouse"
> function and we don't plan to even support it in future releases
> because it's just the wrong way to do things. It's specifically
> prohibited by Apple for development on OS X, for example."
Thanks for the tip, very handy! (I actually learnt this lesson a while
back the hard way). Grab is a great way of grabbin'. Also handling
events in the idle msg loop is now 'out dated, you now use 'send xx to
yy in zz" is EXTREMELY powerful, creating your own delayed events. I'm
sure you have discovered this one too... requires a bit of thinking when
you get lots of msgs queued up etc.
Anyway seems like the 'sticky mouse' is something else: I had it in a
stack with almost no scripts etc. Still trying to track down the exact
recipe. Thanks again anyway.
Thanks Jim!
M@
Matt Denton
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
