LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
_carl

"Find" -> "Class Constant" option

Status: New

I often want to find any cube-dropped class constants for a particular class on block diagrams in my project.  But, to the best of my knowledge, there's no easy way to do this. It'd be great if there was an option to find these when right-clicking on a class in the project:

 

class finding option.jpg

13 Comments
wiebe@CARYA
Knight of NI

>So, I would be curious about the actual use case of searching only class constants.

 

Yes, we could use a more powerful search tool (like Search utility for LabVIEW).

Petru_Tarabuta
Active Participant

Thanks for pointing out that my statement wasn't fully accurate. I agree that the ability to search and find those other methods of instantiation would also be useful.

"So, I would be curious about the actual use case of searching only class constants." - Finding all object constructors when using "simple" / "classic / "static" instantiation. As opposed to the "dynamic" instantiation methods listed by avogadro5.

 

In other words, finding class constants is one part of finding all places where an object is instantiated, and this is useful.

wiebe@CARYA
Knight of NI

It would make sense to allow searching for class constants, controls and indicators, indication (or allowing to filter out) dynamic dispatch controls\indicators (as these can only live in the class, and these are not interesting to find).

 

For dynamically creating classes, you'll get a LabVIEW Object, and it's not required to find this as it's like any other parent class. We're not interested in object types, but in class types. A LabVIEW Object can be any object type (so can a variant or flattened string), but to do anything with it, a cast is needed to get a class type.  To do something (child object) specific with a (parent) class, you'd cast to the child class, which we would be able to find.