Typedef "Value" Property Node issues to fix, please!

[X.]

As discussed here and here, it is annoying that a Value Property Node of a typedef is not typed properly (*).

Related or not, as discussed here, it is annoying that when you try to create a typedef constant for a typedef control, you have to actually do that from the Terminal. And the problem is compounded byt the fact that you cannot access the terminal from a Property Node! It is grayed out. A specificity of typedefs. All other Controls/Indicators terminals can be access by right-clicking any of their property nodes.

Thanks for reading.

Tested in LV 2011

(*) definitely not new in LV 2011

[AristosQueue (NI)]

I have filed these as CARs:

CAR #318066 -- Implicitly typed property node Value does not retain the typedefness of the original control

CAR #318065 -- "Find" popup problems on implicitly linked property/invoke nodes when original control is a typedef

 The first CAR has existed for a while. The second is new in LV 2011.

[X.]

Thanks. Hopefully these CARs won't get parked indefinitely in some obscure LabVIEW bug garage...

[AristosQueue (NI)]

The Find one won't... someone started working on it yesterday. Not sure about the Value one. We did some initial investigation ... it appears at first glance to run deep and seems to have been there a long time. May be tricky to patch up.

Seems amazing, but I couldn't find any record of anyone having reported this bug in the past.

[G-Money]

Moved to CAR database. CAR#318065

[X.]

Is "Declined" the appropriate denomination for a bug that is being worked on? I am just thinking about a potential bug reporter seeing a title reading "issues to fix, please!" followed by a "Declined"... Not very motivating.

[Peter_Hopeful]

The "not find terminal" is not the only problem.

Its more awfull when you have a property node and use "Link to" to change the property node to belong to another control which has a type definition.

In this case the control does not know about its added property node.

The code works until you replace the control. Now the fun starts: the property node disappears. Only when this results in broken wires you will notice this!

[X.]

Peter, can you clarify what you are doing (step by step)? I have tried a few things based on your diagram, but I can't reproduce your problem (I am using LV 2011).

Considering that the thread as been labeled as "Declined" (and the original problem has a specific CAR), you may want to post this as a separate thread (definitely link it to this one, so that the two problems can be consolidated). I am just concerned that it will stay below radar if we continue discussing it here... (plus I can't give you kudos!)

[AristosQueue (NI)]

X: I've pinged the developer of the CAR to stay aware of this thread.

[Peter_Hopeful]

X: to clarify the problem, I have posted a step by step explanation see here

[Roy_F]

The "declined" staus referenced above is saying this "idea" is declined, the issues raised were really bugs and CARs were filed. The two CARs filed as a result of this discussion are not "declined". (In fact, both are fixed in 2012 and will appear in the 2012 bug fix list. Check the 2012 behavior before getting too ecstatic.)

Roy