[Migrated content. Thread originally posted on 15 September 2009]
It is nice that acu allows you to use the same control name and ID in a character screen as a graphical. However, when we do tab screens we try to emulate those tabs with physical character screens since there is no character tab control.The issue we get is that we can no longer use the same control name without getting generate errors. Changing all the control names forces additional coding that provides no real additional benefit.
We have toyed with using frames and using lots of visible code but again we are left with lots of code that is useless. If we could use the same control name on the character screens we would not need any other additional code except that to run the additional character screens.
As an example if I have 2 tabs for a customer program of address and taxes. I would have 2 character screens, one to handle address and the other for taxes. Since my graphical was 1 screen, the 2nd character screen for taxes will have generate errors for the duplicate control name. Note that the first screen does not since both screens are the same name. There is no second graphcial name since it was on a tab control.
I had hoped that I could do modify and inquire statements against the control-id rather than the control-name but I have had no luck with this. Using the control-id would fix my issues as well since I can use the same control-id on any screen in character as well as on any tab on the only graphical screen.
I know I can use the handle but I need to be able to inquire a handle on the fly of any control on the screen. When I do a before or after procedure getting the handle is easy enough but again, I may or may not be in the control I need to inquire against.
I am looking for alternate coding/thoughts on how to handle the character coding of tabs. We have developed a few different alternatives but nothing that we really want to go forward with.
Thanks to anyone who is able to offer any thoughts or assistance on this.
