08-05-2010 04:21 AM
control(input) should act as indicator(output) and viceversa for a string transmission.is it possible
Solved! Go to Solution.
08-05-2010 07:35 AM
Like this
08-05-2010 07:48 AM
Use a local variable.
(Can you explain your problem in a bit more detail? Maybe there are even better solutions.)
08-05-2010 08:36 AM
I have attached more info.regarding my problem
08-05-2010 09:31 AM - edited 08-05-2010 09:32 AM
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.
08-05-2010 11:49 AM
08-05-2010 11:58 AM
You can do the same thing with a property node.
08-05-2010 12:31 PM
@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.
08-05-2010 12:49 PM
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.
08-05-2010 01:03 PM
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?