6 of 6! Loading the Class - A Class Act in LabVIEW

Рет қаралды 14,296

Күн бұрын

Пікірлер: 33

@panda192012 5 жыл бұрын

I have been looking into labview OOP from many sources and couldn't find anything satisfying. Your series has been excellent and exactly what I have been looking for. I'm looking forward to the actor framework playlist. Thank you very much, this is greatly appreciated. Thank you

@TheJohnStark 3 жыл бұрын

You explain OOP so simple. Truly awesome. The whole series.

@xinzhang1839 4 жыл бұрын

These Videos are really good alternative to Tutorials from NI Website. Easier to understand and a lot of valuable knowledges. I am really looking forward to more videos about OOP from you!

@lirec6 3 жыл бұрын

Many thanks for this series! It has been immensely helpful in my journey to get to know the basics and develop further skill from there. Thank you! Keep up the great work.

@0070102040 4 жыл бұрын

A great series to learn LabVIEW OOP. Please upload more detailed videos for beginners.

@rafaelpf9938 4 жыл бұрын

Very helpful series! Thanks for sharing :)

@miguelsegura1794 5 жыл бұрын

Hey Tom!. Are you planing on making a video explaining subpanels and plugins? If you do, i'd appreciate it so much!

@TomsLabVIEWAdventure 5 жыл бұрын

@Miguel, a video on subpanels is a great shout. Because AF is so modular, my user interfaces are often made up of many subpanels to show the status of multiple actors at once. We can then expand this to show how to dynamically change the panel being shown. I'll add this to the list. Regarding plugins, as an actor is a class, the way you dynamically load an actor is the same as loading a class using the 'Get LV Class Default Value.vi'. - I could do a video on that too.

@empoyenyunik 4 жыл бұрын

Thank you! Very helpful for us beginner in OOP.

@AshishKumar-qe4hq 3 жыл бұрын

Can you make a playlist for jki state machine Thanks

@加油小林哥 2 жыл бұрын

Hello, TOM, your video is very helpful to me, but I still have a question, how can I dynamically find these classes I want after generating the exe?

@maxlist9872 4 жыл бұрын

Great explanation. Only the project will fail in exe with an error. Nobody knows what is missing?

@colin7406 4 жыл бұрын

I finally understand what "abstract" means... It seemed like a complex and mystical word before. IDK why because it was explained to be several times clearly lol. I guess I never reduced it to the simplicity of abstract = the one who is the source of inheritance. Maybe I'm just comfortable with those scary words now! Anyways, should objects still be used if you don't plan on them being used for abstraction or inheritance?

@TomsLabVIEWAdventure 4 жыл бұрын

Hey Colin, so OOP shouldn't always be used where it's not appropriate... That being said, my style of programming means I perhaps use OOP much more than most people think is necessary, however, I know what I'm doing and I'm successful at it. I would urge you to form a comprehensive understanding on OOP (from my channel, and other channels as well in other programming languages), that way you can make more informed design choices. "Once you know the rules you're allowed to break them"

@kothamahesh100 5 жыл бұрын

Hi Tom,Thanks for the video. We have doubts on how different kind of hardware using same vis,I mean dynamic dispatching with much more explanation.Please plan to upload a video though it may be short.

@TomsLabVIEWAdventure 5 жыл бұрын

Hi Mahesh, In this video series, I showed using dynamic dispatch with simulation HW and physical HW. I would recommend downloading the code from my GitHub page (link in the description) and try creating new child classes and expand the hardware capability. Let me know how you get on, and comment a reply to this if you get any issues (or find me on LinkedIn www.linkedin.com/in/thomasmcquillan/). OOP (Dynamic dispatch overrides) are heavily used in LabVIEW (and lots of other OO languages) for hardware abstraction layers (HAL), so rest assured this is a well-recognized technique in programming. :)

@murugesanvadivel4331 11 ай бұрын

Very detailed.. Thanks

@tolgahannsusur2534 5 жыл бұрын

Thank you for videos but still I cannot believe that OOP can make me faster on programming. I already have polymorphic VIs and proper subVIs. I have never need to use classes before but I want to make myself believe I need to use it OOP for future but this kind of easy examples makes me think that we could do this without classes in 1-2 min.

@TomsLabVIEWAdventure 5 жыл бұрын

There is an up front cost (in time) to design and implement your classes. However, classes have many benefits: as applications change, classes allow you to append additional requirements to your code without changing already tested and working code. In-fact, if you design your code well, you can append additional features and functions just by making a class-plugin architecture without having to change a single block diagram in your application. I would like to challenge you to design your next [suitable] application using OOP and implement it, the more you use/practice OOP the more you will understand why OOP is a fundamental design practice. If you still don't like OOP after that, then that's okay - it's not for everyone.

@Zettaminx 5 жыл бұрын

Thank you! Love the explanation. Could you discuss the best use of accessors to dynamically access private data, in a future video?

@TomsLabVIEWAdventure 5 жыл бұрын

Glad you liked it :) I'll add that to my list. But in short, Accessor VIs are a wrapper for bundling and unbundling the object. These VIs are very helpful if a child class needs to use the private data of a parent class. With this in mind, Accessor VIs should always have a protected access scope (the scope with the yellow key)