Text issues

[_Bryan]

Kind of a strange one here.

In my program I have a popup dialog that asks for a work order number and you can either scan it using a barcode reader or type it in and then the program stops and turns a process station boolean true.  That part works as expected.

The problem is that if I type in text (but not hit enter) and press the cancel button the boolean still goes true.  But if I turn on highlighting the program works fine.  The reason I want to do this is that if an operator starts typing in a work order and then decides to hit the cancel button the boolean goes false so I do not process the station.

I am thinking it has to do with LabVIEW processing the text box before the cancel button.  But the cancel button had to be pushed to start processing the text.  But with the diagram highlighted it must do things different than regular runtime.  So I do not know how to get around this.

I have tried a few different ways and even with event structures, but could not get the boolean false if there is any text in the box when I press cancel. 

[JÞB]

From the String Right click menu:  Deselect, "Update value while typing"  Select "limit to single line"

Replace the polling loop with an event structure configured for String Value Change and Cancel value Change.

(Trouble:  Start manual entry then change focus and hit cancel.... There is a way around this if it is a problem you need to solve)

[_Bryan]

---

@JÞB wrote:

From the String Right click menu:  Deselect, "Update value while typing"  Select "limit to single line"

I have already done that

Replace the polling loop with an event structure configured for String Value Change and Cancel value Change.

I will have to try this 

(Trouble:  Start manual entry then change focus and hit cancel.... There is a way around this if it is a problem you need to solve)

Yes, this is my current problem

---

[_Bryan]

Reading the trouble part again, that is not exactly my issue.  It is to start manual entry and then click cancel, not change focus then hit cancel. 

I tried using the event structure again with no luck.  I still think it might have to do with LabVIEW processing the text box before the cancel since technically the text value would register a value change as soon as the cancel button is pressed.  It seems that it should be easy to do with the original snippet I attached, unless I am missing something really simple here.

I am using LabVIEW 11.0.1f2 if that helps any.

[_Bryan]

This is a little goofy, but it seems to work.  By adding the shift register with an additional element it lets the text box process and then on the next iteration register the cancel button.  Is this expected behavior?

I am still wondering why the text box and the cancel button do not process on the same iteration.  The highlight execution mode must change the way the text box is handled and process both at the same time making it work properly.  Either way unless someone can help with a better soloution this will have to work.

Thanks 

[RavensFan]

There is a race condition because you can't control when the string control is read vs. the cancel button is read.

What you should use is an event structure.  One case handles the Cancel button value change.  The other handles the String value change.

[_Bryan]

I tried that, but could not get it to work.  If there is any text entered in the text box when the cancel button is pressed the text gets processed first, not the cancel button.

Could you provide an example?  I seemed to be challenged at progrmming this afternoon.

[JÞB · Accepted solution]

Try something along these lines.

(Silly snippets I need to go get the CCT Again.... While I'm doing that try the attached)

[_Bryan]

---

@RavensFan wrote:

There is a race condition because you can't control when the string control is read vs. the cancel button is read.

---

Shouldn't the text and cancel button be read on the same iteration?  The cancel button is forcing the value change of the text box by being pressed.

[_Bryan]

---

Jeff·Þ·Bohrer wrote:

Try something along these lines.

(Silly snippets I need to go get the CCT Again.... While I'm doing that try the attached)

---

Thanks for a starting point Jeff, I did not think it would be this difficult to do.  With my barcode scanner it works with numbers but for some reason it does not like text, it just leaves it off.  Or if I scan in all text it just stays blank.

But I will tinker with it to see if I can make it behave the way I want.

Thanks again.