Creating a child class. Right clicked the class and selected "VI for Override." Selected one of the Dynamic Dispatched VIs from the Parent. What's bugging me is why is the Parent VI included into the new Override VI? Am I using the VI for Override the wrong way? I would have thought it just made a block diagram with all the proper controls and terminals and that's it. But the Parent VI is there. Why's that? In the snippet... CHMBR is the parent VI. I don't understand why that would be included into the Child Override. What am I misunderstanding/doing wrong?

LabVIEW

Why are Overrides Made this Way?

@LuminaryKnight wrote:

Okay, so the misunderstanding is it's just a default thing. No programming rules are being broken. Just delete it and move on. Just seemed weird the very override VI it'll be overriding would be included.

It's quite common to want to "do the same as before, and some more", the 1st half is easily done with Call parent.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems

Message 11 of 11

(128 Views)

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

LabVIEW

Why are Overrides Made this Way?

Re: Why are Overrides Made this Way?