Howdy, > Date: Fri, 20 Feb 2004 20:09:37 -0600 > From: "J. Landman Gay" <[EMAIL PROTECTED]> > Subject: Re: Scrolling a Card? > > On 2/20/04 5:53 PM, Christopher Mitchell wrote: >> Could you please explain under what circumstances this handler would >> require to be explicitly declared? This seems like something implicit >> to the engine, and if not handled reliably then how many other things >> need to be re-defined? > > That's not exactly how it works; it isn't about defining but rather > about access. ------------- Not sure what you're thinking of here. Christopher's actual post looks like this:
***************** > Date: Fri, 20 Feb 2004 17:53:43 -0600 > From: Christopher Mitchell <[EMAIL PROTECTED]> > Subject: Re: Scrolling a Card? > > Klaus, > > Could you please explain under what circumstances this handler would > require to be explicitly declared? This seems like something implicit > to the engine, and if not handled reliably then how many other things > need to be re-defined? > > Yours, > Chris > On Feb 20, 2004, at 4:17 PM, Klaus Major wrote: >> >> on mouserelease >> mouseup >> end mouserelease ****************** ...So, I think the only thing he was referring to was the doubling up of the mouse events, IOW, he was questioning why a mouseUp, then a mouserelease that refers to the mouseUp. It does look suspiscious if he doesn't know what's actually happening Here's hoping he reads on to this. For Christopher: Here's the deal. In Rev, mouseUp messages only take place within the actual control object. IOW, if the user drags the mouse ouside the object and releases, the _object_ not get a mouseUp message. Consequently, if you want to be sure Rev gets the mouseUp message (or some other message related to releasing outside the object), you need to handle the mouseRelease message as well. Take a look at mouseRelease in the dictionary. All the best, Ken N. _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution