LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Quick Drop and Class Name

I'll talk to LabVIEW R&D and see if I can make sense of the behavior. In the meantime, as you experiment, you don't need to restart LabVIEW every time you want to test a palette change. You can call the 'Refresh Palettes' method of the Application class.

Message 11 of 15
(356 Views)

Was there any feedback from LV R&D on this?

0 Kudos
Message 12 of 15
(181 Views)

Quick drop seems work better in a Project. E.g. for finding such VIs.

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 13 of 15
(174 Views)

@NRiver wrote:

Was there any feedback from LV R&D on this?


Unfortunately no, I wasn't able to gather any more information about this behavior.

0 Kudos
Message 14 of 15
(159 Views)

Thanks, that's a shame.

 

In this case I decided to prefix the functions in the library rather than add the libraries (which are in vi.lib) into the project to take advantage of the better quick drop as @Yamaeda pointed out.

 

Another benefit of the prefix is that it also easily gives you a way to browse the APIs of a lib through quick drop, though I do agree that prefixes on file names like that are not the prettiest....

Message 15 of 15
(137 Views)