I think there is my problem. I can not leave the rendering up to anything except my own code. I can not simply add standard Form controls to a renderer and say 'go'. I have all custom controls that have, embedded in them, standard Form controls, but around them I have containers, other controls etc. I have to have 100% control over where the control is rendered (I am mirroring a Windows app). So it looks like the control that governs the tabbing only looks inside Forms? Right now, the tabbing jumps to two buttons I have that don't even have TabIndex set, and they are at a higher level in the DOM tree than the controls I am working with. I have a very complex layout in order to replicate what we are doing in the Windows program. This particular area where the tabbing isn't working is inside a popup window. But even then, the controls are buried a few containers deep inside the window.
So I can rule out the use of the Form, is there another way to control the tabbing? My custom controls all have Form controls in them and I was setting the TabIndex of that control in order to determine the tab order (has to match the tab order of our Windows app). Oh, and none of this is done ahead of time, it's all read from a database and created on the fly. Our customers are the ones that create the forms and I have to render them in whatever condition they create them. Thanks, Jim On Wed, Nov 16, 2011 at 7:29 AM, Alexander Steitz <[email protected]> wrote: > 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 > ------------------------------------------------------------------------------ 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
