Thank Alex, this is the way I expect it to work but it doesn't (at least in my app). Tabbing only happens between 2 buttons and no other controls even though many of them have the TabIndex set. Those that don't are readonly controls that should not get focus. If I place the cursor inside a control that does have it's tabindex set, then hit Tab, focus jumps to the buttons which are outside the grouping of the input controls. And unfortunately my windows are too complex to create a sample to demonstrate this.
Thanks, Jim On Wed, Nov 16, 2011 at 11:47 PM, Alexander Steitz <[email protected]> wrote: > Hi Jim, > > On Thursday 17 November 2011 00:05:07 Jim Hunter wrote: >> 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? > You can define the tabbing order for every widget in qooxdoo. The Form widget > does this out-of-the-box so you do not have to add custom code. > >> 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. > You can set the "tabIndex" property for every widget you like to control the > tabbing order. In qooxdoo there are focus roots. E.g. a window widget is an > own focus root which means that if you tab along inside the widgets of this > windows you never leave the window widget with your focus. > The application root is another focus root and the widgets inside such a focus > root get internally their own order of tabbing (depending on rendering order > and other criterias). > >> 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. > The "tabIndex" property should work. This property should control the tabbing > order. You have to make sure that every widget you create has to have a > tabIndex property set. Otherwise the order in which the widgets were added has > more priority. > > Regards, > Alex > > ------------------------------------------------------------------------------ > 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
