Key navigation changes mechanical action

[devchander]

Hi Nishanth,

Can you please specify what mechanical action of switch do you need in your VI?

And, do you want to use keyboard to initiate it?

[Nishant]

Hiii, Dev

       I am using Latch when released mechanical action for the key, bcoz i want 2 use it as a trigger key and for that i have to use the Latch action, another thing is yes i am using the keyboard action to initiate it.

Thanks,

Nishant

[devchander]

Does not the Keyboard_opt.vi in my previous posts in this very thread, serve your purpose?

[Nishant]

Hiii, Dev

            Ya, your last thread of Keyboard will work for me, but as i told you earlier that it might be generate the load on my vi, which is not barable to my vi, and i think that is why i am finding the simple solution??????

Thanks,

Nishant

[devchander]

Hi Nishant,

As of now,i can only see these two options 'keyboard initialise' or 'events' for controlling mechanical action of button using a keyboard.

Let's see if others come up with better options.

Sorry, I could not be of more help

Regards

Dev

[Nishant]

Hiii, Dev

     Its OK man, don worry, actually, this should happen defaultly, i don know why it isn't??? can you explain why it is not happening? coz if anyone want to take the reference of it than, how he can do such things? its shouldn't be the matter of Latch actions, how it can create the problems??

If i wont find anything else i ll go for the option u ve given.

Thanks,

Nishant

[tst]

As Dev said, I think the only 2 viable options for getting information from the keyboard is through the event structure or the input VIs. The input VIs shouldn't be putting a great deal of stress on your CPU unless you don't have enough of a wait in your loop. Try placing a wait of a few ms. Keep in mind that if you have a wait, every time you click the keyboard it will have to be at least as long as that wait if you want to gurantee catching the click. This is another reason why events are preferred - you can't lose events.

I didn't understand what it is you're trying to do, so I can't offer any real solution unless you explain in more details (and maybe with an example).

[Nishant]

Hiiii, tst

             Let me explain you my problem, actually i am using this key as a Trigger Event key, means if key will press trigger will come, same as event(if event occurs, this thing will take action like that), and i am also referring that key to the stop key for the reference that, if start key's value is true or false with Local variable, but bcoz of Latch action, it is not allowing me to do so... and why i am not using the event structure is the load on my vi already has, coz i am calling lots of global variables in the vi....

Thanks,

Nishant

[tst]

I still don't understand. You want a trigger, I realize that much, but I don't see how the local variables come into it and how you want to stop. What you might want to do is change your action to a switch action and use something like this change detector to find which direction the change was.

If this doesn't help either, you should explain everything you want, step by step and in detail.

[zilla]

Hello LabVIEW fans, I’d like my users to be able to control the program either with the mouse or by tabbing onto the control (Boolean) and hit enter.  The example found in this thread (bool_key.vi) works for a single Boolean, however have not been able to modify it to where multiple Booleans could be controlled. Meaning the user would tab to the first, second, third, etc boolean to select that action then hit enter to send that command. The mechanical action would be Switch Until Release. If somebody can help please either post up snippets or a copy in 8.5.

Thanks!