Help needed using Case structure

[lucky_k]

I was wondering how to control an  case structure if the condition is false . I was trying to set if the entered string  matches perform the multiplication or else if the string entered doesnt matches just retain the previous value. In directly to say take no action if the string entered is not matching.

-lucky.

[RTSLVU]

Not sure I understand your question but if you want to keep the value of x2 the same if the strings do not match, jusr wire it through the false case insted of using the default value if unwired.

[lucky_k]

Hello RTSLVU,

                     we dont want to display the x value if the entered string is unmatched it should holds its previuos value what was there in indicator. Say for the first time if the entered string matches with the string constant in the code and the value of 'x' is  5 and value of 'y' is 20 the o/p in indicator is displayed as 100. For the second time if the entered string doesnt matches it should still display as 100 i.e the previous vale itself.

[RTSLVU]

Oh, ok then you just need to use a shif register

[RTSLVU]

Or a local variable

[lucky_k]

This is what exactly Iam looking for. But Cant we use this with out the help of while loop. Because I want to insert this piece of code some where in a big part of code so adding a control to the while loop is messing up my code. .

[lucky_k · Accepted solution]

Thank you very much the local variable has solved my probelm..

-lucky

[Dennis_Knutson]

In the original VI you posted, simply move the indicator inside the true case. DO NOT use a local variable

[lucky_k]

Dennis,

           The piece of code(case structure) which i posted is actually inside a for loop and i want to record the data outside the for loop. so I cant move the indicator  into the case statement. Will there be any problem if I use the local variable? or is there any other better way to handle this case.

[Dennis_Knutson]

Then put the shift register on the edge of the for loop.

The problem with local variables is that they are easy to misuse and it's better to learn how to avoid them. Later, when you have more programming experience, you will understand when and how they can be used.