You do well to test your code on new versions. You'll catch the problem if the CVI behavior changes, but you'll still need to fix it. My cautious approach is to avoid using undocumented features.
Using an array of control IDs, unless you intentionally change the group of controls, you don't need to modify the original array. There are no unintended consequences. Using the tab order, you have unintended consequences if you copy a control: your tab order just changed. Unintended consequences are usually unpleasant surprises to anyone else supporting your code. If you intentionally make a change, it's usually easier to catch any problem related to your change.
Sorry I overstated it when I said ANY change in the UI editor could affect your tab order. I was meant copying , adding, or deleting controls. But again, since this is undocumented and we don't have anything written in stone describing the behavior, we don't know what changes will affect the tab order.
To follow your comment about abandoning ship, you should wear a life jacket, not a flak jacket. Here's my analogy.
There are two channels between point A and B. It is debatable if either channel is faster. Channel A is clearly marked and will not be changed. Channel B is not clearly marked (undocumented) and has some submerged rocks. These rocks haven't moved in years, but may at some time in the future. I say "Take Channel A". You say "I'll take channel B. I know where the rocks are. If the rocks move in the future, I'll fix my boat." I wish you smooth sailing!
