DutLUG: LabVIEW Configuration Editor Framework (CEF)

Подписаться 5 тыс.

Просмотров 3,6 тыс.

50% 1

The highest rated LabVIEW training course on Udemy (created my me): www.udemy.com/...
Purchasing the course using this link is the best way to learn LabVIEW and support the channel.
The Dutch LabVIEW user group was kind enough to invite me to talk at their user group about the Configuration Editor Framework (CEF). I had great fun giving this talk so I hope you like it and learn something.
The CEF is a great way of creating and organizing all of the configuration settings for a standalone application or a portion of a larger application.
Links to get started:
CEF Forum Page: forums.ni.com/...
CEF Download: www.vipm.io/pa...
Windows Notification Tray Toolkit: www.vipm.io/pa...
Adobe PDF ActiveX Example: knowledge.ni.c...
Me: / thomasmcquillan
#LabVIEW #DutLUG #Configuration #SoftwareEngineering

Опубликовано:

18 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 16

@BloodstarDE 4 года назад

It's a shame that NI doen't provide that type of high quality content for free. Thanks for having you Tom.

@JeffreyHabets 4 года назад

Thanks for being our guest Tom! It was a great talk and demo and well received by everyone.

@colin7406 4 года назад

Fantastic ! I love that I can watch any video by you and be blasted with quality info. Got me motivated to get out of bed and try this out for switch matrix application 🤔

@dennisvanotterdijk 4 года назад

Thanks for the interesting presentation Tom! Excellent content, properly explained with enough detail...

@BashleyN 2 года назад

I missed this when it came out, but now find myself needing to read up on the CEF so thanks Tom! really useful :)

@CARLIVONNE 3 года назад

Super cool! Thanks for this presentation, it will help me a lot, knowing how to use the CEF and not start from scratch.

@PK-1 3 года назад

Remarkable presentation, thanks for doing that!!

@vishalbajaj4231 Год назад

Hi Tom, Kudos for the amazing video. Can I bother you for a quick question though. How would I go about adding multiple devices like cRIO, DAQmx and an Agilent P.S in the same tree?

@dryfus3031 2 года назад

Hi Tom Can you explain how you created that drop down menu bar in the title bar in your project at 28:33?

@colin7406 3 года назад

If inspiration ever hits you again, I'd love to observe the in depth process of converting the CEF template over to a custom project. For example, is it best to just rename the cRIO classes, or just possibly clone them and move to a "unused folder". I think renaming objects is difficult, unless I'm missing something. I'm wondering how you got rid of the old objects, renaming, deleting, etc. I wonder what the best option is!

@TomsLabVIEWAdventure 3 года назад

Hi Colin, I usually use the GOOP toolkit to clone an existing class, the tool creates a new folder for you in the correct location. Then all you have to do is 'clean-up' the class. It doesn't take too long (5 minutes or so). The only annoying thing is the GOOP toolkit changes the class icon, so you have to update that.

@mariangiuica9011 3 года назад

Hi Tom. Thanks for this presentation. I have a question regarding the nodes. Is the framework providing a way to force a class as singletone? For example to force the user to only have one Group node. Thanks again!

@TomsLabVIEWAdventure 3 года назад

Hi Marian, The framework allows you to have as many instances of a node as you want. However if you wanted to limit the number the user can launch, you could override the 'Menu.vi' (I can't remember the exact name) then you can disable the 'add' menu tag based on the number of nodes launched

@ravidhoble9163 3 года назад

Hi Tom, This is a good start for me, as I am currently working on creating a test sequencer entirely in LV instead of using TS. I really like the UI you created called "TS lite". So, I want to know that The test sequences you have added under the Test Sequence node in the tree are individual Modules Vis having particular functionality required or all information is getting saved in an XML file with the same test sequence name? Can you also give an insight on how the custom test sequencer works? Thanks!

@TomsLabVIEWAdventure 3 года назад

Hi Ravi, sorry for the massive delay in getting back to you (maybe this will help others who stumble across this). Each node is a class wrapped in DVR, each node knows who its parent node is and who the child nodes[] are, so when I sequence through the test routine, all I have to do is get the 'Test Sequence' node, look at the child nodes[], and index through them (using a for loop, and an 'action.vi' dynamic dispatch method).