When you call stop when the mouse is in the scrolling container (scroller is running), the mouseenter and mouseleave (detach) events are removed so detach never gets called! I would expect that stop calls detach explicitly where Scroller is running, and that start calls attach explicitly when mouse is over scrolling container (might be impossible to detect), but it does not do so!
KASI On 17 Jul., 22:51, Rolf <[email protected]> wrote: > Hello Kasi, > > This does seem to work. However, like Sandy I'm not really sure why > start() and stop() should not work. I looked at the code, and it does > do other stuff, mainly adding the mousemove trigger when onEnter (i'm > not yet sure onEnter what exactly though).. > With directly using attach I attach the mousemove event to the > document.body/container I am using. > > Can you explain what exactly happens? My mind has been processing to > much JS lately, that I seem to overlook stuff at the moment. > > On Jul 17, 3:28 pm, kasi <[email protected]> wrote: > > > Use scroller.attach and scroller.detach instead of scroller.start and > > scroller.stop! > > > KASI > > > On 17 Jul., 13:48, Rolf <[email protected]> wrote: > > > > It's really annoying, or maybe I just don't understand how it should > > > behave/work/used. :/ > > > > On Jul 17, 8:07 am, Sanford Whiteman <[email protected]> > > > wrote: > > > > > Just wanted to let you know that I fought with it on your behalf for > > > > past 2 hours. No luck either. Will look at it again tomw. > > > > > --Sandy > > > > > ------------------------------------ > > > > Sanford Whiteman, Chief Technologist > > > > Broadleaf Systems, a division of > > > > Cypress Integrated Systems, Inc. > > > > e-mail: [email protected] > > > > ------------------------------------
