Current it is very hard to reliably manipulate decorations using VI server.
LabVIEW need to be able to create explicit decoration references (like it is possible to do on other objects through right click Create>>Reference).
Note: Thanks to TonP for the idea.
vipm.io | jki.net
This is an illustrated example of essentially what falkpl posted 3 months ago - check out his triple-starred point. I like both ideas... Kudos.
Pauls post says "optional labels so that they can be addressed programmatically", and addressed programmatically pretty much means reference. Either way, I Kudoed both ideas. I'm mainly cross-referencing for the sake of the 3-month old idea... it did not get NEARLY as much Kudos as it deserves, and hopefully some of the post-NI Week craze will go back and read the old posts. So, all of you who like this idea, please go back and check out Paul's New Decor.
NI needs to spend resources on improving the user interface and reducing the hoops the programmer has to go through to fight with LabVIEW to make the front panels look decent. Hopefully the overwhelmingly positive response at NI Week to just minor improvements to the UI look and feel (even if just in keynote demonstrations) will open NI's eyes to how much LabVIEW lacks in the UI development area compared to other coding environments.
Make a difference. Join the UI Interest Group and stay active.
I like this idea, but what happens when you have
(for example) two or more Vertical Smooth Box? I think NI would have to
allow labels on decorations for this idea to be fully realized, or
maybe we could do it with tags.
In your example, if there are 2 (or more) vertical smooth box, I will edit the BD label of the reference decoration and give each one a different name (like I would do if I were to do the same thing with two control having the same name).
Note: It is already possible to edit explicit control reference labels.
So, I don't think there is a need for decoration to have labels.
That old, and no solution. In principle you can access the decorations property. BUT when changing the order on the front panel one will loose the specific decoration one wants to access. And what happens if one wants to make a decoration as type-def (if that is possible)?
My suggestion - if this is important to you today, customize a control (usually a boolean will do) and replace its graphic parts with that of the decoration. Then you can create an explicit reference and make it a typedef.
As suggest earlier, you can also create a psuedo-reference today using tags. There's a JKI RCF plugin which does this in the communities (that plugin is probably what PJM was referring to when he said Ton gave him the idea), but you will have to adapt it if you don't have the RCF. I would suggest going with the control.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.