copy property node in another frame

[oldpan]

Hi everybody,

I have like 12 frames in a case that each will display a message. I want the display to take place in the same string indicator. So I'd like the property node Value of the string indicator to reside in the other 11 cases. I cannot manage to copy the same property node ,issued in the first frame, - the one that I get asks for reference link. Firstly, I find cumbersome to drag a reference from case to case(I don;t know how to do it cause I don;t have any local to pass it), secondly, I know there is a keyboard trick with which one can actually do the copying of the property node that doesn't require for the reference.
If you will tell me  the trick with ctrl key and dragging stuff, then you have to be more explicit cause I tried it and didn't work.

Thank you very much,
Dana

[GerdW]

Hi Dana,

did you try the ctrl-mouse click&move as suggested before (I think in one of your threads)?

But:
You should redesign your vi to: put the string indicator behind the case structure. Make the string an output of the all cases. When the string doesn't change use a local. When the case is inside a loop don't use a local but a shift register instead!

[falkpl]

Can you refactor the cod so that the property node is outside the case structure and each case passes a different value out of the case structure?

Paul 

[oldpan]

Hi all,

Thanks for the support, the advise are really helpful.
Here is how I eventually did: I created the Value property node, as many as I needed of the same string indicator, and I moved them out of the case frame, in a neutral place, from where I took them each time I skipped to another frame of the case, and link them there.
I used the ctrl key +mouse move that you told me about GerdW, to multuplicate the instances of the property node.

All the best! I'll keep in mind what you tell me, they all also apply for the future.
Dana

[GerdW]

Hi Dana,

even when your vi works now: change to development style to our recommendations.

The vi will be much cleaner, less error prone, will run faster (property nodes have their disadvantages!). Even locals may be better in your case...

[oldpan]

Hi GerdW,

I didn't undestand what you mean by "putting the string indicator *behind* the case structure".

Nonetheless, I have a just-occured question. What property node I have to extract from a Stop button- I extracted one called 'Indicator" but running the application proved to me this was not a good idea- Do you know which one applies for the same situation of having the same button for all the 12 cases , using a suitable property node for this?

Thanks again,
Dana

[GerdW]

Hi Dana,

it's the same problem as before:
read the stop button before the case structure and put a wire into the case structure. No need to read the button in each case!

At the moment I don't have LV at hand, so I cannot look at your vi...
But in general: for each property you will find a text in the context help! "Indicator" tells you if the button is a control or an indicator... You surely want to read it's "value". But again: if you really intend to read the button in each and every case, put it before the case (or use locals, if nothing else helps).

[oldpan]

Hi again GerdW,

Sorry for not sticking with the original, the rationale was that the subject of the post should be related to the content. If I stick to the original, one that searches the 'variant' problem will find no interest in the different-titled post..

The mechanical mode , if I get your point , is pressing - and it is the button that stops an infinite while loop. Is this the answer you need?

Regards,
Dana

[GerdW]

Hi Dana,

right-click the button on the front panel, in the lower half you find an entry "Mechanical action" (or similar). What did you choose there?

Latching operations don't work with locals...

[oldpan]

The settings show "Latch when released"

Dana