LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Create and open type def in one step

I am always making typedefs. They're super helpful and make my code much easier to modify. However! I must right click and select Make Typedef, Then right click again to open the type def and save it. This is annoying. Under what circumstance would I create and then not also open and save a typedef? My preferred behavior would be that when I create a typedef, the control is immediately opened for modification and saving. In fact, the prompt to save might pop up automatically as well.

 

Maybe someone has create a quickdrop shortcut for this.... 

_____________
Creator of the BundleMagic plugin for LabVIEW!
0 Kudos
Message 1 of 6
(214 Views)

image.png

 

Maybe not exactly what you ask for but might save you some time if check "Open the control editor with double click".

 

George Zou
0 Kudos
Message 2 of 6
(200 Views)

@littlesphaeroid wrote:

I am always making typedefs. They're super helpful and make my code much easier to modify. However! I must right click and select Make Typedef, Then right click again to open the type def and save it. This is annoying. Under what circumstance would I create and then not also open and save a typedef? My preferred behavior would be that when I create a typedef, the control is immediately opened for modification and saving. In fact, the prompt to save might pop up automatically as well.

 

Maybe someone has create a quickdrop shortcut for this.... 


A close second to that annoyance is that it always creates the typedef at the top level of the project instead of in the library of its "host" so you always have to drag it into the correct library and change its icon.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 6
(192 Views)

@billko wrote:

A close second to that annoyance is that it always creates the typedef at the top level of the project instead of in the library of its "host" so you always have to drag it into the correct library and change its icon.


Here is an idea I posted to correct that:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Type-Def-made-inside-a-library-VI-should-be-part-of-t...

 

Regards,

Raphaël.

0 Kudos
Message 4 of 6
(183 Views)

I gave it a vote.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 6
(176 Views)

@littlesphaeroid wrote:

Under what circumstance would I create and then not also open and save a typedef?


I rarely make type defs anymore since I switched to OO. 

 

Just an occasional enum, but never clusters...

 

When I do create a type def enum, I simply mark the enum as type def, and wait for LV to ask me so save it when I close the VI. So for me this is a rather convenient workflow, although it's not clear what is saved first (esp. in the even rarer case where you marked 2 controls as new type def).

 


@littlesphaeroid wrote:

Maybe someone has create a quickdrop shortcut for this.... 


It's sooner look into LabVIEW Shortcut Menu Plug-Ins - NI Community.

 

This can actually replace LabVIEW's menu (if you want it to). You might get it to do exactly what you want.

 

It's a bit tricky to get going with shortcut menu plug-ins, but what you request doesn't sound too difficult.

0 Kudos
Message 6 of 6
(115 Views)