I have found a couple problems with tables that I've worked around in my app,
and which may be relevant. I haven't had time to look into these enough to
file proper bugs. FWIW, these may have been fixed already in 1.0, but
perhaps they'll give you and others some useful leads.

- If you make the table widget draggable, you will get ghostbuster symbols
when you click on the headers to sort. The solution is to override the
tablePaneScroller and make it draggable, rather than making the table widget
draggable.

- The focus indicator eats events under IE, causing the context menu event
to never fire. I disable the focus indicator like so, and the events flow
fine: 

  table.getPaneScroller(0).setShowCellFocusIndicator(false);
  table.getDataRowRenderer().setHighlightFocusRow(false);    

- I have had to patch table/columnmenu/Button.js to make the column menu
appear the first time the right mouse button is clicked. The patch is to
explicitly add the "appear" listener when the factory method creates the
menu. I don't remember exactly what was going on here, but it seemed like it
was some issue of the listener not getting set up properly in some cases.
This is difficult to reproduce because it has something to do with the
specifics of my table. Without this patch, the context menu appears as a
tiny rectangle with no contents. This has been discussed in the forums
previously, BTW, without resolution.

Hopefully this helps someone.

Dave

-- 
View this message in context: 
http://n2.nabble.com/Bug-in-qx-ui-table-Table-cellClick-event-handler-tp4554907p4555316.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to