LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

read and write(control should act as indicator and viceversa)

Solved!
Go to solution

control(input) should act as indicator(output) and viceversa for a string transmission.is it possible

-------------------------------------------------------------
kudos welcome
0 Kudos
Message 1 of 30
(3,614 Views)

Like this

 

 

20729i4143C67E7DFD2149

Tim
GHSP
0 Kudos
Message 2 of 30
(3,593 Views)

Use a local variable.

 

(Can you explain your problem in a bit more detail? Maybe there are even better solutions.)

0 Kudos
Message 3 of 30
(3,585 Views)

I have attached more info.regarding my problem

-------------------------------------------------------------
kudos welcome
0 Kudos
Message 4 of 30
(3,569 Views)

Do NOT rename a bitmap image to png to get around the ban on bmp files! Play by the rules.

 

You've already been given the answer so explain what your problem is with using the solution given.

0 Kudos
Message 5 of 30
(3,555 Views)

Perhaps you don't know how to create a local variable:

 

20745i188CB0514D534A45

- tbob

Inventor of the WORM Global
0 Kudos
Message 6 of 30
(3,533 Views)

You can do the same thing with a property node.

Tim
GHSP
0 Kudos
Message 7 of 30
(3,527 Views)

@aeastet wrote:

You can do the same thing with a property node.


Yes you can.  But property nodes are much slower than local variables.  For simple programs, you won't notice the difference.  But sooner or later, you will encounter a case where too many property nodes will noticeably slow down the code.  It is considered bad programming style to use property nodes instead of local variables.  Property Nodes work through the UI thread.  Locals do not.  So locals present a lot less overhead. 

 

It is best to not get into a bad habit from the start.  Use local variables instead of property nodes.

- tbob

Inventor of the WORM Global
0 Kudos
Message 8 of 30
(3,519 Views)

 

Yes you can.  But property nodes are much slower than local variables.  For simple programs, you won't notice the difference.  But sooner or later, you will encounter a case where too many property nodes will noticeably slow down the code.  It is considered bad programming style to use property nodes instead of local variables.  Property Nodes work through the UI thread.  Locals do not.  So locals present a lot less overhead. 

 

It is best to not get into a bad habit from the start.  Use local variables instead of property nodes.


I do use local variables and think it is ok but there are the people on here that think they are the worst thing ever invented. Also it is not bad to show a couple of different way to do things so the OP can learn different ways to do things. Property nodes are something that you will inevitably have to learn if the OP wants to do real programming.

 

Tim
GHSP
0 Kudos
Message 9 of 30
(3,513 Views)

As I have said in numerous posts, local variables are not bad.  Improper use of local variables is what is bad.  You can also have race condtions with property nodes, so they can be just as bad.

 

Its OK to show various methods of doing things, as long as you specify the shortcomings and advantages of each.  It is bad if you show a bad habit and don't explain that it is a bad habit.  DON'T use property nodes for writing values.

 

Can I call for other opinions about local variables and value property nodes?

 

- tbob

Inventor of the WORM Global
0 Kudos
Message 10 of 30
(3,509 Views)