jgcode Posted December 14, 2009 Report Share Posted December 14, 2009 What is the best way to handle methods in X controls? As-far-as I am aware there is no system information for the method invoked available. Do people pass in an enum from the Property VI to identify the method and do the work in the Display State Change event of the Facade? Cheers -JG Quote Link to comment
Ton Plomp Posted December 14, 2009 Report Share Posted December 14, 2009 What I normally do is set up a messaging scheme. When a property is set (or read) or a method is invoked, I add a cluster with a string (specific to the property/method) and a variant (with specific data) to an messaging array in the display state. In the facade VI I read the message and act appropriate. system information for the method invoked available What do you mean with 'system information' Ton Quote Link to comment
jgcode Posted December 14, 2009 Author Report Share Posted December 14, 2009 What I normally do is set up a messaging scheme. When a property is set (or read) or a method is invoked, I add a cluster with a string (specific to the property/method) and a variant (with specific data) to an messaging array in the display state. In the facade VI I read the message and act appropriate. Thanks Ton That sounds really clever - kinda like Producer-Consumer comms What do you mean with 'system information' I mean LabVIEW providing us with information that this method was just run/selected by the user. 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.