08-29-2022 09:12 AM
Similarly, I've made the habit of having a static dispatch "Create" function, where again, the parent and child can have different kinds of inputs. It serves some of the same purpose as the "pre-init" Intaris described, and allows me to call "Init" with few or no inputs (because the needed data was already stored in the object during "Create").
-Kevin P
08-29-2022 09:29 AM
@Kevin_Price ha scritto:
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW?
@Kevin_Price: Why your "warning" message?
08-29-2022 09:55 AM - edited 08-29-2022 09:57 AM
If you have no other choice and have several tens of classes to update, I would try using scripting to automate this task.
However depending on the complexity of the update you made to the mother method, implementing this may get quite complex.
You'll need to inspect both mother method's and child method's connector panes to compare the differences and make the wiring update.
You may also need to create or re-create controls on the front panel using the VI method "Create from Data Type" or "Create from Reference", and wire or re-wire them to the code in the block diagram using the method "Connect Wire" of the Terminal class.
08-29-2022 12:30 PM
@SlippinJimmy85 wrote:
@Kevin_Price: Why your "warning" message?
Sent a PM with a little more info. For anyone else, many of my reasons can be found here, some of them borrowed from other's postings.
-Kevin P