LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

F3 does not trigger "Key Down?" event, but other function keys do.

Hi all!  So, in writing my app I noticed that the F3 key does not trigger the "Key Down?" filter event I have in my Event Structure, but the other function keys (F1, F2, F4-F12) all do.  I can tell because I have an indicator set to show what VKey was pressed and it never shows F3.  It brings up a search window when I'm on the Windows desktop, so the key does work. 

 

Anyone have any idea why LabVIEW finds F3 so special?  I do plan on using some of the function keys in my app, but not having F3 is no big deal; I'm just curious why it doesn't work.

 

This is on LabVIEW 2009 (with f3 patch) 32-bit on Windows Vista 64-bit.

 

Thanks!

0 Kudos
Message 1 of 12
(4,151 Views)

I have no issues with the following code on Windows 7, 32 bit. LabVIEW 2009.1

 KeyDown.png

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 12
(4,143 Views)

Hi J,

 

also no issues (LV7.1 and LV9.0f3)...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 12
(4,138 Views)

D'oh!  I forgot to mention that my event is linked to a string control in my program.  The VI snippet posted by TCPlomp works fine and F3 appears to trigger the event.  However, once I modify that snippet to add a string control and link the event to the control then F3 no longer works.

 

No F3 String Control 04-19-2010.png

 

I don't know why the wires are broken in the snippet any why the Event isn't assigned.  So here's the VI also.

 

 

Message Edited by The J on 04-19-2010 12:23 PM
0 Kudos
Message 4 of 12
(4,118 Views)
The Event case  have no event to trigger off and need redeifining. If F3 is the trigger for a Value change in a string control, why are you not reading the "String" - Value change event?
CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 5 of 12
(4,113 Views)

The event case is properly linked up in the attached VI; however, I don't know why the snippet itself (which is from the attached VI) is broken.  The attached VI is a modification of the snippet that was posted earlier by TCPlomp.  His snippet worked as is, but it showed the same problem when I modified it.

 

I should probably try to explain what I want to do.  The app I'm working on is a serial console.  I use the "Key Down?" filter event on the main text area (console window) of my app because I need to be able to trigger different actions based on the key pressed.  For example, pressing a normal key allows me to just send that character over the serial port, pressing Enter sends the proper line ending sequence (CR, LF, or CRLF), and I want to be able to use the function keys to set up string macros.  Basically, you can map a serial command to a function key and pressing it will send that command plus the proper line ending over the serial port. 

 

The reason why I use a filter event is because I can discard the event if local echo is turned off.

 

I can certainly deal with not having F3, but I'm just curious what makes that key so special.

Message Edited by The J on 04-19-2010 12:47 PM
0 Kudos
Message 6 of 12
(4,105 Views)

Maybe F3 is setup as a special key for your OS on your PC setup by your manufacturer???

- I can't download the snippets 'cos I'm working in 8.6 at them moment, so I'm working on what I could see and think of.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 7 of 12
(4,101 Views)

That's actually what I was thinking, too.  That F3 must be some special key.  In Windows Vista, F3 opens up a search window, so it is a special key in a sense.  Then I found that TCPlomp's snippet does work with F3, which is why I'm curious.

 

Thanks for the responses!

0 Kudos
Message 8 of 12
(4,098 Views)
Since your posting of the code snippet didn't work, can you post the actual code?
0 Kudos
Message 9 of 12
(4,089 Views)

The VI should be in the bottom of the message with the snippet, but here it is again in case it didn't attach correctly.

 

0 Kudos
Message 10 of 12
(4,081 Views)