XControl publish subscribe?

[tst]

I still don't understand the exact problem - just go to all the places in your code where the reference points to the Boolean class and change it to be the Control class, since it doesn't make sense to treat these reference as booleans. You then just need to relink the invoke nodes in the main VI and the code works perfectly fine, at least as far as I could tell - changing the value of the valve changes the appearance of the pipe.

I'm not sure I understand your new suggestion either, but it's certainly possible to assign an LVOOP class as the data type for an XCtrl, so if that's what you want, it's certainly an option. There's also a relevant idea in the idea exchange - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Tag-an-XControl-as-the-default-control-indicator-for-a...

[GabbyG]

There are many ways to overcome that limitation.

Obviously one of them is to handle the Xctrl-Reference of CROSS inside the VALVE-Xctrol like I do with the BOOLEAN references.

But that means I'll have to set up duplicate entries and processing  pathes just because I cannot cast  Xctrl(boolean) to Boolean.

Anyway I'll find a way. Thanks for the link to AQ's proposition. Apperantly it's a bit stale.

Gabi

[tst]

I still don't understand the problem. What's wrong with this modification I made of your earlier attachment? Like I said, the only difference is that the references are of the Control class.

P.S. No, I'm not in the US. I'm probably a couple of hours east of you, so it's not that early in the morning here.

[GabbyG]

Thank your for your patience, tst.

Now I see what you mean. The problem is although I think a bug. Maybe only in 2013.

Dragging my original failing reference + method into your version (back in 2013) gives the same error.

With the funny result that the seemingly identitcal operation flags an error or not.

Re-linking the fails to the same FP-object does not change the error condition.

Creating a new pair it is OK.

Maybe I'll send it NI just for curiosity.

Gabi

[tst]

Just to clarify, by "relink" I meant right click the node and select the relevant option from the menu. I have no option why that's needed (and I don't remember seeing it before), but it's there, so I'm assuming there was a reason for it.

[GabbyG]

Correct.

If you delete the ensemble and recreate it anew it is OK.

If you just right click select link to .... it will stay the same.

Since I am still evaluating what will be the path to follow, I might have updated the XCtrl after pulling it to the Frontpanel ????

I'd consider the case closed, but maybe someone else will stumblöe upon it.

Nice talking to you

Gabi