Utility to "Check dependency for UI Thread access"

[TiTou]

When analyzing execution performance it would really help if we had a simple yet comprehensive way to check a VI and all it's dependencies for "things" that would create a UI thread swap / access.

cheers

[AristosQueue (NI)]

VI Server properties/methods, Call Library Nodes configured to be UI thread, subVIs configured to be UI thread. I can't think of anything else.

[TiTou]

Yes, the point of my suggestion is to have a one-click way to spot all of these.

Does it already exist?

[AristosQueue (NI)]

It's called the NI-User. Users can be deployed for all sorts of tasks, including checking a VI Hierarchy. 😉

Ok... joking aside...

No, no such inspection tool exists *directly*. But writing a VI Analyzer test to check for such things should be straightforward, and then you just run it over your hierarchy. (Note that I'm suggesting this workaround but not closing the idea.)

[TiTou]

My turn to make jokes : this is the LabVIEW Idea Exchange, not the VI Analyzer Idea Exchange.

Joke aside, my wish is to have something that ships with LabVIEW (no extra coding nor toolkit required), just a menu option on the VI to scan it with it's dependencies.

[jtagg]

Do all VI server properties and methods go through the UI thread, or is that a general statement that has some exceptions?

[crossrulz]

Only properties and methods for front panel items go through the UI thread (as far as I am aware).

[jtagg]

That's also what I thought, and why I'm asking. As far as I'm concerned the trickiest part to programmatically determine whether a VI needs the UI thread is a list of which properties and methods use the UI thread.

[crossrulz]

It is not the list of properties and methods, it is a list of classes that is needed: VI, Control, Pane, Panel, Decoration, whatever I missed.

[AristosQueue (NI)]

All VI Server properties/methods go through the UI thread. In other words, the properties/methods of any class that inherits from Application, VI, or GObject (both panel and diagram).

[AristosQueue (NI)]

TiTou: VI Analyzer is part of LV Pro. It's not a separate toolkit. If we were going to implement a feature like this, I can pretty much guarantee that it would be a part of LV Pro (pretty much anything that works on "whole hierarchies" instead of "single VI" is Pro).