Replies: 2 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
-
|
You really aren't missing anything. These VIs are thin wrappers around calls to LabVIEW's C code. They essentially make the operation public, but what they are hiding is the mechanism used to call LabVIEW's C code. Even if we made a public way to call this code in the next LV release, that wouldn't help the older versions that the icon editor supports. In order to eliminate them we'd have to wait until the icon editor's oldest supported version was after the operations where made public, so we're talking years in the future. If this is causing some limitation, we should focus on what you are trying to accomplish rather than on passwords as being the block. I'm extrapolating a lot from what you provided but I'm guessing you want to change the type of the data stored in the VI. Pretty sure we could accommodate that. That might mean making this VIs use a typedef that can be modified, but loading old data may mean we need to support multiple types so making the VIMs could be appropriate. I'd say start a discussion on the problem you are trying to solve and we can work out the best path forward. That path is unlikely to involve removing these passwords though. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In the lv_icon.lvlib I found the following VIs are still saved with password protection:
Considering these directly affect the data structure of a VI, NI might need to pull stuff out of these VIs before opening them up.
Beta Was this translation helpful? Give feedback.
All reactions