tab sequence inheritance question

Classic Servoy
1

I have a form that extends a base form, adding a few fields. Is there a way I set the tab sequence of the new fields so that the tab sequence of the base form is honored and then the additional fields in the child form are tabbed-to?

2

JayColey,

This is currently not supported (other than manually editing the underlying frm-files).
I would suggest to create a feature request for this.

http://crm.servoy.com/servoy-webclient/ … oy_support

Rob

3

Has this been resolved in 5.2?

JayColey:
I have a form that extends a base form, adding a few fields. Is there a way I set the tab sequence of the new fields so that the tab sequence of the base form is honored and then the additional fields in the child form are tabbed-to?

What I’m seeing is a bit odd. If I change the tabSeq on the base form, the tab sequence changes on the base form when editing in SC or WC, but not for inherited fields on any child form. On the child form, the sequence for inherited fields appears to be what ever it was when the child form was first created from the parent, or possibly the order of the fields in the underlying table. Even odder, the observed tab sequence on the child form differs from SC to WC.

Any suggestions?

4

On further testing it appears that the tab sequence on the fields from parent form is ok until I edit the tab sequence on the child form.
Setting the tab sequence back to default on the child form fixes the tab sequence on the inherited fields.
Anyone else seeing this?
I’m running 5.2 developer on Mac OS 10.6

5

Tony,

The problem with tab sequence in form hierarchy is that the sequence is stored with the elements.
For example if you have a superform {field1: 1, field2: 2) and subform (field3: 1) the flattened form contains (field1: 1, field3: 1, field2: 2).

If you edit a subform you cannot change the tabindex on elements on the superform because that would affect other subforms of the superform.

We plan to address this in a future version (has someone filed a case on this already?), but for now the workaround would be to manually assign the tab sequence in the frm-files and use gaps: superform {field1: 100, field2: 200) and subform (field3: 50) if you want to add the field inbetween fields 1 and 2 or subform (field3: 500) if you want to add it a the end.

Rob

6

Thanks for the explanation Rob.
Could we also use something in the Solution model to set tab seq correctly at runtime?

7

Yes, the tabSeq (int) property on elements can be set using the solution model.

Rob