Excellent suggestion. I will give that a try tomorrow. Thanks, Jim
------------------------------------- Hi Jim, I had a similar problem a while ago -- where a real mouse event would trigger a listener, which would then update a widget that threw the same event, and get lost in a loop. I am not sure if this is the most elegant solution, but I ended up adding a piece of state to event objects that are constructed and thrown by listeners. The piece of state indicates whether or not the event is a result of a raw mouseevent. Listeners can then look for that piece of state in events that they hear, and behave appropriately. I.e., your listeners can distinguish between real mouseevents and "second-order" generated events. Hope this helps, Simon ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
