Find Control in Event Structure doesn't show the object when it is not in the frontmost Tab page [Bug Report, LabVIEW 2012]

[X.]

When you are looking for the control/indicator handled by a case in the Event structure, you can use the contextual menu item "Find Control" (doesn't distinguish between control and indicator, BTW).

The result is that the control/indicator is highlighted on the FP. The problem is, if that control is in a Tab and specifically in a page of that Tab that happens to not be the frontmost, the only thing you'll see is marching ants, but no control:

<=========== the wrong TAB page was shown. LV did not bother to switch to the relevant one....

In other words, "Find Control" in the Event Structure doesn't switch the tab to the owning page. This is contrary to what happens if you right-click, say, the terminal of this control: the FP will switch to the owning Tab page.

I'd call this a bug and this is definitely an annoyance (which most likely has been around since the creation of the Event Structure).

[altenbach]

Please attach a simple example that demonstrates the problem and also add an entry to the monthly bug thread.

Why should support need to wire up their own VI from scratch just to try to reproduce the problem that pontentially might depends on random other stuff??

[X.]

It is so trivial to reproduce that I did not think it was worth it.

Attached.

[X.]

Is anybody at NI going to file that as a bug or is it one of these features that LV users will need to learn how to leave with?

[altenbach]

Did you add an entry to the monthly bug thread? I cannot find it.

[X.]

I did not. Is there any better chance for it to be caught there by a NI eye than it is in the LV forum? I though these threads were deemed to gather bugs/features that had been already acknowledged by NI with a CAR number.

I (and others!) wished there was something like this: http://bugs.sun.com/ or http://bugs.python.org/ for LabVIEW...

I am just coming back from a short conference of scientists who quite uninamously ended up with the conclusion that LabVIEW was to be disregarded as a lab development environment because of maintenance problems (which could have been argued for any language in my opinion, although I think they meant spaghetti diagrams are the natural tendency of students who could not care less as they are not going graduate because of their LV skills or lack thereof), but I guess I could have added my grain of salt and added the complete opacity on bug and feature handling by NI.

[dstrandb]

Hi X,

Thank you for finding and pointing out this behavior. I've taken note of the behavior of the Find Control command, and I will look into some documentation to see if this has been documented before. If not, I will pass this information along to our R&D department so they are aware. In the meantime, I might follow altenbach's suggestion of posting this to the monthly bug thread. That will increase the exposure of this behavior. Thanks again.

[X.]

OK, thanks.

I'll just point out that until acknowledged as a bug, a feature is just that, a feature. So it may or may not belong to the monthly bug report thread.

I uncover a lot of these "features" and sometime just give up the idea of reporting them, because there is (in my experience with this forum) no guaranty that these reports will go anywhere.

The feedback can any of these typical experiences:

- no reaction. I post a few comments to my own post, some random user posts some random comment.

- quick NI reaction that is out of topic or just shows that the guy is new to LV and did not understand what the problem was.

- interest from NI, but requests a more detailed report (with example VI etc) and then nothing.

- CAR issued shortly after my post.

[X.]

Still alive in LV 2015