F15 Keystroke & Labview

[dacad]

Trying to track something down here and am wondering, does the F15 (function 15) key have any impact on Labview when it is running ?

Key stroke could be actual or virtual.

Trying to think outside the box on something.

[Knoxberry]

Doug,

It depends on your operating system and what you are trying to do. On Mac OS X, the <F15> to <F24> function keys are reserved so you wouldn't be able to use them as shortcut keys. I believe <F15> on Mac OS X adjusts the contrast, but I'm not 100% sure. On Windows, you should be okay to reassign the function keys to whatever you like (in LabVIEW). If there is a default action for the function key, you should be able to configure your application to handle the key press event and discard it.

What behavior are you trying to prevent? Or what exactly are you trying to do? You could also just attempt pressing the <F15> key on your computer to see if there is any response.

Regards,

[RavensFan]

Where is F15 on a keyboard?  Mine only goes up to F12.

[0utlaw]

Hi RavensFan,

Mac "large format" keyboards go up to F15 (these are in place of the printscreen row on PC keyboards) - Haven't tested it, but I seem to recall you can also simulate these keys with a shift-modifier on the normal function row.

Regards,

[dacad]

I asked without explaining the circumstances to try and get unbiased input, sorry if that was misleading.

Reason is, I have been having bizzare behavior with an application that has been running on an win xp system for years with no problems. It ran with LV 8.6 and 2011 and never had an issue.

Fast forward to now and I am having to update to a win 7 system (32 bit) so I figure I'll update to LV 2013 at the ame time.

I start getting erratic slowdowns in the application test sequence where sometimes it slowed the actual sequence and sometimes just put delays in the front panel updates.  After some time, I discovered some of the front panel updates were being delayed by exactly 1 minute, multiple times during each sequence.

Then I started experiencing erros with an analog write routine to my daq. (pci-6014)  The error pointed to the daqmx-wait-until-finished.vi   which didn't make sense becasue I had a full second added to the time out versus what the task was alloted to do.

I have had posts for both of these issues going since last week or so.  In trying to leave no stone unturned on what would have changed, I looked at what else was running on the new system.  I routinely install and run a utility called Caffeine that stops the screen saver from engaging by, here's the connection, performing an F15 keystroke.

This is where I made this post.   Ultimatley I went further and discovered that it made that F15 kestroke every 59 seconds (too close to my 1 minute screen delays to be coincidence)

So yesterday, I completely disabled and unloaded the utility and all seems to be working well. I have along the way rewritten some code but am going to do some trials with the very original version to determine if the Caffeine was indeed the root cause.

I have since downloaded a different utility to keep the screen saver from activating that uses small mouse movements instead of a keystroke.

I am not able to change the corporate mandated screen saver settings so get around such follies the best I can.

Thanks for the responses and again, I apologize for intentionally leaving out information, I just wanted to make sure I wouldn't taint the responses and perhaps miss some outlying connection.