07-19-2017 12:50 PM
Hi HopeH
I probably wasn't clear. Your example -its good, but it not editable in run mode (directly) It is selecting from an already written list Another way to say is what if you didn't know what the user wanted to enter?
07-19-2017 12:55 PM
So just wire up whatever it is that the user selected. What is the problem you are having with that?
07-19-2017 01:02 PM
If you are going to allow a user to redefine what a button means, how do you plan to associate their naming conventions with the actual functionality of that button? Sounds like you might want to limit their options instead before it gets completely out of control. #users * #options * Upper/lower case * misspelling * ...
07-19-2017 01:18 PM
yes - i know that HopeH. I just didn't want to add any more"stuff" if it was unnecessary and the caption itself could be used as runtime text box. Didn't mean to go so far with this
Thankyou for your thoughts
07-19-2017 01:22 PM
Ohhhh, I finally get what you mean. You are wanting the user to directly enter text into the caption to edit it. Yeah, I don't think there's any way you can do that... But it's not really much of a complication to add code for how the caption should be set, I don't think, and, as Minions said, you probably won't want it to be exactly as a user typed, but you might want to have them just pick from options to set the caption or something like that. Good luck with your application!
07-19-2017 01:39 PM
We have several products that have similar interfaces except that they have completely different names based upon the customer. Based on the interface that connects to the UUT, we have a custom set of captions that appears to the user for each unique product. We have the captions stored within a configuration file and then load the correct set based on the UUT interface. This way the look/feel can be changed to accommodate the user; however, the underlying functions and connections are consistent and the naming remains consistent as well once the product is finalized.