LAVA 1.0 Content Posted September 4, 2006 Report Share Posted September 4, 2006 This may also be a feature, you never know what NI engineer intend when they make their design decissions. Class probes can access to private data members of the class. However class probes cannot access private or protected member methods of the class. Workaround is to make methods public, but then the methods will also be visible to class user which really spoils the idea of private and protected methods. Quote Link to comment
Aristos Queue Posted September 5, 2006 Report Share Posted September 5, 2006 Class probes can access to private data members of the class. However class probes cannot access private or protected member methods of the class. Workaround is to make methods public, but then the methods will also be visible to class user which really spoils the idea of private and protected methods. This was reported to R&D (# CAR 4148NNJ1) for further investigation. It is confirmed as a bug. Custom probes should have the same access as any other VI in a library (or any deriviative of library, such as class or XControl). Quote Link to comment
LAVA 1.0 Content Posted September 5, 2006 Author Report Share Posted September 5, 2006 This was reported to R&D (# CAR 4148NNJ1) for further investigation.It is confirmed as a bug. Custom probes should have the same access as any other VI in a library (or any deriviative of library, such as class or XControl). I have not verified if this is only a problem with (public) classes inside a library or a more general issue. Quote Link to comment
Aristos Queue Posted September 6, 2006 Report Share Posted September 6, 2006 I have not verified if this is only a problem with (public) classes inside a library or a more general issue. I did verify it ... it is a general issue. 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.