LAVA 1.0 Content Posted September 11, 2006 Report Share Posted September 11, 2006 This may be a feature, not a bug. One may define class inside a library to be public or private. Public classes can be accessed from outside the library and private classes only from inside the library. When on defines ancestor class to be private and decendent class to be public, it's not clear if the inherited methods will be private or public. In LabVIEW 8.20 these inhereted methods are private and inaccessible outside the library. This means that even though the class is public, some of its public methods are inaccessible, since they are defined in a private class. I think that if a class is public, then all its public methods should also be public, no matter if they are defined in a private class. That is, if a public class is derived from a private class, then the private class should become public in methods but the class constant should remain private. Dynamic VIs should require a public class to be connected to dynamic dispatch input terminal. -jimi- Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.