extend default reference of property\invoke nodes

[wiebe@CARYA]

An unwired property node of class VI defaults to the current VI.

An unwired property node of class Applicatio defaults to the current Application.

Why does an unwired property node of class Panel defaults to the current VI's panel?

This only makes sense to have for these classes (and some scripting classes not mentioned here):

Application

VI

Panel

Project

only to these classes it makes sense, because a VI will always have exactly one! Well, not Project, since a VI can exist outside a project, but it still makes sence to me to default to the current project if it's there...

[crossrulz]

You obviously haven't played around with splitters.  Your VI can have more than one panel.  The splitters split your front panel into many panels.  Therefore, it doesn't make sense to have a default of "this current VI's panel" since LabVIEW doesn't know which one you mean.

[wiebe@CARYA]

You obviously haven't played around with splitters.  Your VI can have more than one panel.  The splitters split your front panel into many panels.  Therefore, it doesn't make sense to have a default of "this current VI's panel" since LabVIEW doesn't know which one you mean.

You are wrong. Splitter make panes. There is only one panel.

[crossrulz]

Oops.  That's what I get for not double checking myself.

[AristosQueue (NI)]

A VI can only have one panel *today*. 🙂

[wiebe@CARYA]

If we are going to get a MDI interface, I dont mind if this doesn't make it.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.