Ctrl key

[tbilir]

I am having a problem where sometimes my ctrl- based keyboard shortcuts are not registering the ctrl key.

It doesn't matter if I use left or right ctrl.  All other keys are fine.  I previously narrowed it down to a particular activeX object which probably used too much memory, but now I'm finding the same problem with a program that has no activeX.  If I close the offending VI, other VIs behave normally with respect to ctrl.  

I read about overlapping controls (from Tab containers) possibly causing the problem, but I can't understand why that would be (or should be).  I'm wondering if anyone else has encountered this problem, and what if anything might help.  I am seeing the issue on multiple computers, all running Win10 with LV2018.  

[Kyle97330]

Can you actually post the VI with the problem?  The actual VI, not a screenshot.

If it has a lot of subVIs or dependencies on toolkits or drivers that the average user might not have, attempt to remove them first.  This has the added benefit that if removing one of them makes your VI start working again, you now have a better idea of how to fix it.

[tbilir]

Hi, 

Thanks for your reply.  I can't post the actual VI since it contains proprietary information for the client.  However, I can describe the structure.

Essentially I have a QMH which is underlying a multi-step process.  The process is controlled and via front-panel tab container such that each step has a single tab associated with the controls and indicators for that step.  The steps are executed through a subVI in the QMH.  

When I recreate a similar VI, things operate normally for a while, and then eventually bog down.  I am hoping that there might be a configuration setting or possibly hardware change that could accommodate whatever is causing the control key issue.  It just seems like a very weird symptom.  All other commands work normally.  E.g. cut and paste work just fine from the drop down menu, but hotkey doesn't work.  

[Kyle97330]

Is there anywhere on the block diagram an event structure containing a "Key down" event?

[tbilir]

No.  All events are Control:Value Change except one standard panel close.

[altenbach]

What are "my ctrl based shortcuts"?

System shortcuts (ctrl+c, etc.)?

Key navigation?

QD shortcuts?

Something else?

[tbilir]

Sorry I didn't see this earlier.

All of what you described below.  QD doesn't work, switching between fp and bd (ctrl-e), clean-up (ctrl-b), cut and paste (ctrl-c, ctrl-v).  Essentially anything with a ctrl for the shortcut.

These functions all work normally from the drop down menus, but who uses those?

T

[altenbach]

Well, obviously something is intercepting these keys (you say "multiple computers". If only one I would have said "replace the keyboard" :)).

• Is it the same problem if you close down LabVIEW completely and then open a new blank VI?
• Do you have special third party enhancements installed, e.g. screen capture utilities, keyboard utilities, etc.)
• Do you have any unusual accessibility settings in windows (sticky keys, toggle keys, filer keys, etc.)

[tbilir]

The problem does not happen if I only open a blank VI.  This only happens after loading significant VIs.

Never happens in other programs, even while large VIs are loaded.  

Doesn't happen in small VIs in LV if I load very large other programs (i.e. it is not a system RAM issue)

Machine: Dell Optiplex 7050 with 7th Gen i7, 16GB RAM, Integrated Graphics (128MB Intel chipset)

I'm running stock Windows 10 Pro, and I don't think I have anything special going on, but it is controlled via IT.  I know there is an antivirus from the IT department.

[tbilir]

Also, I noticed that if I open a large VI after a restart, ctrl-keys work a few times before stopping.  

I tested this by just Ctrl-e switching between front panel and block diagram, just back and forth until it didn't respond.

After the response dropped, I was able to get the ctrl-e to work if I waited ~1 second, held ctrl for ~1 second, and then pressed e.  

T