Feature Request: clicking on an error should highlight the node in the diagram

[labviewette]

Dear Development Team,

one thing that is better handled in LabVIEW in comparison with LabVIEW Comms is that when clicking on a complilation error LabVIEW highlights the subVI in which the error occured whereas in LabVIEW Comms the subVI is directly opened. The disadvantage in LabVIEW Comms is that one needs to search for the faulty VI in the Diagram by himself which can be pretty time consuming.

Kind Regards

[National_Burritos]

Hi labviewette,

Just to be clear, your setup: you have a main VI that calls a sub VI. There is an edit-time error in the subVI, which shows up as edit-time error in the main VI which says "error in subVI". When you double-click on the error, it opens up the panel of the subVI when in LabVIEW Communications. Your desired behavior would be to highlight the subVI on the diagram of the main VI instead of opening it up, which is what happens in LabVIEW?

Regarding having difficulty finding the faulty VI - if you just do Ctrl-F (find)  on the main VI, and search the name of the subVI, it will highlight it for you. You should know the name since it opened up the subVI.

I think the reasoning behind this change was so you could get to the root of the error and fix it more easily, though I will definitely pass this feedback onto R&D to get their thoughts as well continue to improve the product.

Cheers,

[National_Burritos]

Hi labviewette,

From following up with R&D, our thoughts were that we think this work-flow makes sense - and I am curious if you agree, especially since you can find the broken subVI in the main diagram in other ways. In LabVIEW, we highlight the broken subVI. What's always your next step? Open it up and see why it's broken. We tried to think a little more about the workflow and tried to serve that need when designing the LabVIEW Communications environment. If you have further thoughts though, I am more than happy to hear and pass that on!

Regards,

[labviewette]

Hello Rahul,

Thanks for replying. I agree that once an error was detected in LabVIEW the natural work flow is to open the broken subVI in order to fix it. Still for me personally it is an important "extra" to know where in the Main VI did this error occur, especially when dealing with nested structures, as an example.

In LabV Comms I find it pretty weary not knowing where the broken subVI is in the Main VI. As a side note: searching for this subVI only highlights it in the files pane but not in the Main VI. So as i gather: there is no way to highlight the faulty subVI in it's calling VI.

Kind Regards

[National_Burritos]

Hi labviewette,

Thanks for the reply! As I mentioned, I did pass this on to R&D. Thank you for providing some more detail on the use case! 

Regarding searching - when I am in the diagram, if I hit Ctr-F and then type in the name of a subVI, it will highlight it/allow me to scroll through all instances on the diagram. If you use the search in the palette area, that will only show you the subVI in the palettes. Is this different than what you see?

If you are not able to search the subVI in the diagram, this might have been a feature added in the 1.1 version? If you are working in LabVIEW Communications 1.0, I would update to 1.1 here: http://www.ni.com/gate/gb/GB_EVALLVCOMMS/US.