> I then tried to do it the 'correct' way and use the selectionChanged > event and it fires 100% of the time, but since I set the currently > selected row for each table (to visually show the user which row in > each table is selected) when I create the tables, it fires the > selectionChanged event on that table which causes a total chain > reaction that never ends. So, when you have many tables, and you need > to accurately respond to users clicks and you need to show the > selected rows, how do you do it? There has to be a simple thing that > I am overlooking but I'm not seeing it.
If you have to set the selection by API but don't want to react on the selection event why don't you simple set a flag before changing the selection and clear it after the call. In your event handler you can check this flag an just do nothing, when it is set. This way your handler reacts when the selection is changed by the user (flag is false), but does nothing if the selection is changed by you (flag is set). ------------------------------------------------------------------------- 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
