DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Automatically create a subvi when creating a new Event

At least for what I've made so far (what I pictured), I really like the cleanliness of having the class wire as the data. No in place element structures or unbundle-bundle to worry about for dozens of states. But yeah I did see that edit. By-and-large that does seem to be the solution that will work better and be more developer-friendly. The class data method does have that specific use case of if you're making a module for an already established class-based driver IMO.

 

@OP, if you are still dead set on making subVIs that have the entire module data on the connector panes (keyword if), then something nearly as effortless but requiring zero scripting would be to make a template VI that you can File > Save As... over and over again, whenever you make a new Request. You'd really want to be good with your documentation and best practices though. Two best practices that might help with that: don't wire the indicator terminal if the data doesn't change (as explained in this article), and going along with that, add "(dup)" to any indicator terminal that is definitely a duplicate of what came in.

Redhawk
Test Engineer at Moog Inc.

Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.

Message 11 of 11
(416 Views)