Make text search look inside error ring constants

[joerg.hampel]

The error ring is a great and simple tool to define errors, especially when selecting "Custom Error Message" and supplying parameters from outside of the error ring.

The fact that the text search doesn't look inside the error ring makes it hard to find hard-coded error codes. 

Idea: I would love to see the search in LabVIEW also find strings inside error rings. 

PS: This idea (or inspiration for it) comes from Stefan Lemmens.

[AristosQueue (NI)]

This is a good idea. Kudos from me.

Unfortunately, I thought it might be a quick thing to fix, but a first glance at the code suggests it might be rather a lot of programming -- it'd be the first time the search has ever been asked to look inside G plug-ins. Worth doing, but might be a fair time commitment, so might be hard to be a priority. I'll flag it for consideration, though.

[joerg.hampel]

 Thanks for the feedback and the background info, Stephen. 

[wiebe@CARYA]

As long as you'll be looking into the error ring and text search:

+ Are timestamps (%T, %<%M>T, etc.) supported by the error ring jet?

+ When working on the text search, please make it stop searching 'raw' data. I have (e.g.) several pixmaps constants (and\or controls\indicators) that slow the text search down by a few 1000% (e.g. few minutes iso few seconds). At least in LV2013. Even worse, the search won't even find binary data that matches the pixmap's data, so the search time is just wasted.

[AristosQueue (NI)]

%T (and its variants) have worked I think from day one. I just tested in LV 2018... %<%M>T specifically works.

[wiebe@CARYA]

AQ: Sorry about that. I knew there was something 'wrong' about those error rings. But not timestamps.

Enums are a problem. So a %s in a Format Into String will accept Strings, Enums and Booleans. The error ring will only accept strings. Might be an idea on it's own (unless it's already in >2013).

[wiebe@CARYA]

>Enums are a problem. So a %s in a Format Into String will accept Strings, Enums and Booleans. The error ring will only accept strings. Might be an idea on it's own (unless it's already in >2013).

Posted here: Error Ring accepting Enum. Sorry Joerg for the thread hijack. Will ping back to this.

[paul_cardinale]

---

@joerg.hampel wrote:

The error ring is a great and simple tool to define errors, especially when selecting "Custom Error Message" and supplying parameters from outside of the error ring.

The fact that the text search doesn't look inside the error ring makes it hard to find hard-coded error codes. 

Idea: I would love to see the search in LabVIEW also find strings inside error rings. 

PS: This idea (or inspiration for it) comes from Stefan Lemmens.

---

I created a tool to do just that.  I would be happy to share it, but there's no way to attach a file here.

[joerg.hampel]

I just stumbled upon this plugin made by hooovahh: https://forums.ni.com/t5/LabVIEW-Shortcut-Menu-Plug-Ins/Error-Ring-Search/ta-p/3715693

Inspired by pcardinale / paul_cardinale (sorry, didn't see your post - thanks for chiming in):

https://forums.ni.com/t5/LabVIEW/Error-Rings/td-p/2337862

[Rikko]

paul_cardinale,

Is there any way we can get the tool you mentioned?  

[joerg.hampel]

@Rikko, the links are in my last comment (the one right before yours).