The same should probably apply for the short name, but it isn't. So, you can't override and specify a different long name. If we didn't change the long name in the menu, then the end user wouldn't get what the developer intended. If we changed the name in the menu, it would appear you're using a different property. the menu you get when you click a property node) are populated based on the long names from the property node's class and all parent classes. This is because the properties in the property selection menu (i.e. Third question, how do I localize the long name and short name, not likely I am going to do that but just in case I might? Second question is that do the names in an inheritance hierarchy need to be the same or is it enough that the DataName is unique? If there are conflicting definitions for long name and short name, will LabVIEW show an error? I ask this because if I create a class, specify the long and short name for a property, then someone creates a child class for that class and wants to override the property accessors, does he or she need to set the long and short names to be exactly the same or would LabVIEW use those of the parent class that first defined the property? But how do you have an access to all those names in the class editor (LabVIEW project)? ![]() Now I assume I know how to change those names in scripting and editing lvclass files. Thanks Mike, that was a comprehensive answer. ![]() Let me know if you need more information. I hope that sufficiently explains the names associated with a property node. Here's a first second draft of something I typed for a KB: All are exposed via scripting three are exposed in the editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |