By the way, I've a little question about the panescroller. In order to make my new table's headerrenderer work properly regarding mouse events (click => sort, mousemove => column move), I had to subclass the default panescroller because there was new widgets inside the table's headerrenderer that should behave properly.
I was wondering why the mouse events management was only located in the panescroller class. Why not delegate it the the headerrenderer directly ? Just to avoid modifying the panescroller too. It's just a quick suggestion/idea, I know that the panescroller must also take into account the column resizing part etc... - I don't analysed all in details (but I also suspect I'll be forced to subclass the paneheader in order to manage correctly the columns' "dummy copies" when moving it... Any reason ? Best, Benoît. -- View this message in context: http://qooxdoo.678.n2.nabble.com/possible-bug-in-qx-ui-table-pane-Header-tp5555625p5558195.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
