I have the same problem, but time is a bit smaller, 1 second or less (I have quite powerful CPU). I think it's qooxdoo issue, because it happens in Firefox and Chrome and it's always first scroll.
On Thu, May 13, 2010 at 3:06 PM, fx5 <oodx...@fx5.de> wrote: > > Hello, > > when i use the mouse-wheel for the first time in my application the whole > interface gets unresponsive (with high cpu usage) for a few seconds (about > 4s in Webkit or 10s with Firefox). When i use it again, everything is fine. > > Is this a bug or just slow? Is there a way to work around? > > Maybe I can turn off mousewheel-events for the whole application? > I tried to add an EventListener to the root-widget and called stopProcessing > for the event, but with no luck. > > Or maybe i can trigger a first mousewheel-event at start-time of the > application? This would prevent the interface becoming unresponsive while > the application is running. > > Thanks in advance > Frank > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Mouse-wheel-making-interface-unresponsive-for-a-long-time-tp5045998p5045998.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Best regards - Petr Kobalicek <http://kobalicek.com> ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
