How to set up enter key function for a touchscreen device (no keyboard)

[LuisRuiz]

Hi. I'm quite new with Labview. 

I'm trying to modify a VI to be used on touchscreen devices, but I'm having trouble with this:

There are two buttons on my front panel, let's call them "A" and "B". Button A executes the command "Count" while button B is used to "Record" the count. Using the keyboard, I can press "enter" key for "count" (A) and press "enter" key again if I wish to record the value (B). Now the user needs to use the VI without the keyboard (in a touchscreen). 

I think when there was a physical keyboard used, the "key focus" (not sure if I have that correct) was moved from one boolean to another.

The easiest option would be making button A and B big enough so they can be manipulated with a finger and place them together in the front panel, but the user needs to have only one big button to perform both actions (first click for "count" and second click for "record") as "enter" key does when using a keyboard. Is this possible?

If it is not, maybe there is a workaround placing buttons A and B overlapped and programmatically move B over A after the first click, or create a "C" button that controls A and B as desired (I don't even know if it is possible to do something like this)

Any suggestion would be highly appreciated.

Thanks in advance. 

PS: I'm using LabVIEW 2014 32-bit

[RavensFan]

If you have large buttons on a touch screen, what is wrong with them hitting A, then hitting B?

I imagine your code is using an event structure to act on whenever A or B has a value change event.  Do you?

If you want a third button C, you could do that, and have the event for C programmatically fire the events for A and B using the Value(Signalling) property node.

But overall, if you have a VI that is running on only a touchscreen with no keyboard, you should design it for the user interface you have, not some hybrid VI that  might be a keyboard/might be a touch screen.

[JÞB]

If that is the flow,  press button to start process A, press  button to start process B. What ever is wrong with a single switch type boolean?  If true A. If false B.

A custom radio button would be more scalable though.

[LuisRuiz]

Thank you both for your response. 

The VI I'm working on has been designed for a mini laptop used on distillation tower gamma scans, on which using enter key was possible to "count" and "record" if you like the result (there is also an "ignore count" function). Now This VI needs to be used on tablets, the thing is this jobs are performed under any weather condition (raining, snowing, etc), where the user may not be able to look at the screen, for this reason a big and unique button is preferred. 

The easiest solution I found was overlapping both buttons and use the property node:visible to make them visible or not at my convenience, what's more, the new VI can also be used on laptops (user requirement).