Concerning bug(?) when retrieving control references from typedef

[parsec]

I seem to have encountered a bug which could make a lot of my work less reliable. Could anyone shed light on this behavior?

I am attempting to obtain properties from controls within typedefs programatically, however the control/tabbing order set in the typedefs seems to be affecting the order in which the control references are obtained in an erratic manner.

 

I can produce two seemingly identical typedef clusters with the same control/tabbing orders displayed whose control references are not in order.

Please see the attached image.

[G-CODE]

Do you observe the same behavior if instead of returning the 'AllObjs[]' property from the cluster and typcasting each to a control , you return the 'Controls[]' property instead?

[parsec]

Thanks! That fixed it. Why are the refs in AllObjs out of order like that?

[Yair]

AllObjs[] uses the Z order, not the tabbing order. My understanding is that this is because it can include objects which can't be tabbed to, like decorations, so they're not part of the tabbing order. The same applies to SelectionList[] properties (although those also group items you selected together in a higher hierarchy).