Leaderboard

Where the hottest LabVIEW ideas flow... lava, LabVIEW, (data)flow... get it? I got nothin'...

The International Association for the Advancement of LabVIEW Development LAVA - Where new ideas in LabVIEW flow freely... Most Awesome Graphical Magical Algorithms (MAGMA) Very original LabVIEW concepts about neat objects (VOLCANO) Highly evangelical algorithm topics (HEAT) Topics enhancing concepts to optimize National Instruments code (TECTONIC) ok, some of those are pretty bad...

I've never really like using "is a" as a measure of whether a class should inherit from another class. I think it's too loosely defined and easily leads to design problems that are hard to resolve. The Circle-Ellipse Problem is an example where it breaks down. That could be the right business decision and I'm not criticising it, but be aware it is probably not the correct architectural decision. At the very least you'll be losing some readability. More likely the problem you've run into indicates an error in your design. If this code is going to be supported and extended over the long-term you'll probably end up wishing you had fixed it. Personally if I had to make a quick fix I would have gone with Shaun's solution. Move all the code from Parent.Operate into a new method, Parent.Operate(Shared), and have Parent.Operate simply delegate to Parent.Operate(Shared). I can't say definitively it's a better solution, but instinctively it makes more sense to me.

Hit the diagram cleanup and you'll see exactly what your problem is. It would help you if you changed the direction of the fb nodes (right click option).

I'm coming to this discussion after NI Week and having listened to the topic reverberating off the walls post Stephen's session. FWIW, I think those who think this is a bug or "should be changed anyway" are confusing the concept of timeout with the concept of "Default (Case)". Timing out the Event structure is not a guaranteed method to "catch" any and all unspecified events and why should it be, esp if a timeout is given to constrain it. An event is an event and, while each event will have a timestamp, none are polled but all are received -- regardless of the action taken by the structure. It's up to the programmer to "clean up the mess" he/she creates in registering the event. An unregistered event is STILL an event -- and can't NOT be an event. It's just not a very wisely programmed event: like an uncaught setjmp() back in the REALLY old days always "set your gets before you get sets into your code".... Ok so that's just two cents worth from a non CLA who is, in many ways, really old school so this is text and not in cool graphics.