Hi Jim, an example of how to use the "Form" is available at
http://demo.qooxdoo.org/devel/demobrowser/#ui~FormRenderer.html The main idea about the form is that this is only a logical grouping of widgets. The rendering of a form is delegated to a form renderer instance. The order you add the widgets is the order how they are rendered / layed out. So if you use e.g. the single form renderer the tabbing should work out-of- the-box. Regards, Alex On Wednesday 16 November 2011 02:28:02 Jim Hunter wrote: > I am trying to solve a tabbing issue and I thought that, if all the > controls I want to group together in tabbing, then the tabbing would > work correctly. What is currently happening is that when I tab while > in a control, it jups out of the 'area' and up one container to a > button. So, I thought if I grouped them in a qx.ui.form.Form, then > they might tab correctly. But what's happening is that by simply > including this one line of code below, only half my page renders. I > don't get any errors, I just don't get some of my controls. > > var test_Form = new qx.ui.form.Form(); > > if I simply remove the line, everything draws correctly. > > Any ideas what may cause this? This is my first use of a Form, am I > going about this correctly? ANy better way to group controls so that > they tab correctly? I'm open to suggestions. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
