LabVIEW
ComboBox constant autoupdate - suggestions?
Maybe you should refer the customer to this topic and explain why what that requirement is a dangerous one?
Why would you consider this requirement dangerous?
The customer wants to preserve all settings (e.g. constants) even though he updates the list of registers.
It will be up to the customer to update the constants (either manually or automatically).
@RavensFan wrote:
@pitol wrote:
It will be up to the customer to update the constants (either manually or automatically).
Do you truly expect that customers will ALWAYS to what they are supposed to do?
You need to protect yourself, your code, and the equipment your code is working with, from changes that the customer forgets to review.
I don't know what you're talking about...
My customers are always perfect 😉
@pitol wrote:
Why would you consider this requirement dangerous?
The customer wants to preserve all settings (e.g. constants) even though he updates the list of registers.
It will be up to the customer to update the constants (either manually or automatically).
Sorry I didn't get back to you earlier. Thank you for re-explaining it to me. It's always dangerous when you and the customer have responsibility over modifying the code. I'm thinking legal issues, too - because, if you can both modify the code, then who really owns it?
I still think an enum is better because you make the new ID which breaks the code, then you fix it by either duplicating the case that the ID duplicates, or by adding the new item to the appropriate case. Then when the customer is ready to delete the old ID, they delete it from the enum which breaks the code, then go fix it where it's broken. I believe that's the easiest, and safest, way to do it.
Thank you all for your responses.
I think we covered the topic thoroughly 🙂
Knowing the advantages of enums I still choose Comboboxes...
Why?
To make it short, lets assume that I am going to deliver single VI to the customer who will use that VI in his application.
That VI performs some action.
The VI contains one input, which is the register ID.
My requirements for that input are:
- it shall allow user to select register ID from drop down list (the typedef)
- it shall allow user to type register ID manually
- it shall preserve selected value if the typedef is rebuilt
To all of those requirements the Combobox seems to fit perfectly. Enum is ok, but at some cases it will not preserve the previous value.
Anyway, I've done it and it works as planned.
Thank you all for meaningful discussion.
