"Nick Glencross" <[EMAIL PROTECTED]> writes: > Hi! > > We've got quite a lot of qooxdoo code now, and it's working great! > However, I've still got a couple of unresolved niggles which I haven't > been able to find workarounds for. Any hints would be great: > > * I haven't successfully worked out how to make Enter in a form > submit it. There's a previous posting which shows how to do it by > sending the keypress event onto the submit button, but things must > have changed because the value of the text field that you are in > doesn't get correctly picked up. I can provide a test case to > demonstrate this if it helps.
Have you tried using qx.client.Command() for this purpose? I think it should be appropriate. > * It's been discussed on the list a few times, and I've been hoping > for someone to suggest a resolution (if they have, I missed it). What > I'm wanting is a way to present URLs in tables and TreeVirtuals, and I > don't mind turning off selections if that's what it takes (but I > haven't managed). URLs in Tables work in IE with a custom renderer, > but not in Firefox. In the TreeVirtual I've tried an HTML link, but > the selection is obviously overriding it. Hmmm... If you needed only a single URL in a single row, it's easy to catch the Selection event (an event is already dispatched for that to any waiting listeners), and do something with the url. In that case, you'd likely keep the url in the data model (whether displayed or otherwise) and access it via something like this untested snippet: // Get the list of selected nodes from the event var selectedNodes = event.getData(); // In single-selection mode, there will be only one selected node var selectedNode = selectedNodes[0]; // Get the column data that contains the url (for example, use column 2) // With just-checked-in code, you can now use this to retrieve the data var columnData = tree.getDataModel().getColumnData(selectedNode.nodeId, 2); // Use the data, presumably in a nicer way than this: location.href = columnData; If you don't want the actual URL displayed, you could generate a custom Cell Renderer that displayed columnData.text, whereas the above would change to location.href =columnData.url One more thought: If your cell renderer always renders the clickable "thing" (href, icon, etc.) in a known place, you can use the mechanism demonstrated in qx.ui.treevirtual.SelectionManager's _handleSelectEvent() method. It determines whether you are clicking directly on the open/close icon or someplace else in the cell. A similar mechanism could be used for detecting clicks in other cells. Cheers, Derrell ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
