![]() ![]() With this design NI is actually limiting the usage of password protection.įor me the correct behavior is such that when a VI is password protected, then its implementation is hidden and nothing more. I think this is not how it should be as it limits the usage of password protection to only those cases where you want to lock the context as well. Now it seems that NI has added a second meaning, namely locking the VI context as well. Password protecting a VI has until now meant hiding the implementation of the VI. It could be on a block diagram of another VI etc. This feels like a bug to me.Īctually I think NI is mixing two different concepts here, namely protecting the VI and locking the VI context.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |