Troubleshooting
Fixing Press-and-Hold Right-Click in HMI Apps on a Touch Panel
Short answer
If press-and-hold opens the right-click menu in Notepad but drags a control inside your HMI or CNC application, the touch panel, its driver and the Windows gesture setting are proven good — the application is capturing the touch as a drag. The fix is a correction to that application from its vendor, not a driver change; in the documented case, a patched KMotionCNC.exe for KMotion435c resolved it.
On this page
Press-and-hold opens the right-click menu in Notepad after roughly 500 ms, but inside the HMI or CNC application the same hold drags a text box across the screen. That combination is the diagnosis: the touch surface, its driver and the Windows gesture are all working, because Notepad would fail with you if any of them were broken. The application is reading the touch contact itself and treating it as a drag, so no driver reinstall, recalibration or hold-time tweak will change it. The fix belongs to the application's vendor — in the documented case, a patched KMotionCNC.exe for Version KMotion435c copied into C:\KMotion435c\KMotion\Release, after which the press-and-hold menu opened in the G-code display. The tests below take about ten minutes and eliminate one layer each.
The Notepad test and what each outcome proves #
In the Windows touch model, press-and-hold is the system's substitute for the right mouse button: keep a finger still, inside a small movement tolerance, for the configured duration, and Windows itself synthesizes the right-click. Notepad honors that, and so does every plain Windows application. That gives you a one-minute layer test — press and hold in Notepad, then press and hold on the failing control:
- Notepad opens the menu; the application drags its control. Gesture, timing and driver are proven good. The application handles the contact directly — close the timing question next, then go to the vendor correction. This is the documented case.
- Nothing opens a menu anywhere. The gesture is disabled or slowed past a usable hold. Fix the setting first, then retest Notepad before touching anything else.
- The touch cursor never appears at all. That is the digitizer link, not a gesture problem — video can arrive over HDMI while the USB touch channel is dead, and why HDMI video works but USB touch does not on a panel covers that fault.
Keep the finger still for both halves of the test. If the finger drifts, Windows cancels the gesture by design and every application, Notepad included, sees a drag. None of this depends on sensor technology: the gesture lives in Windows, not in the digitizer, so a resistive panel and a capacitive panel fail and pass this test identically.
Where the gesture setting lives #
Two places control press-and-hold on a Windows panel:
- The feature toggle: Settings (Win+I) → Bluetooth & devices → Touch.
- The duration: Control Panel > Hardware and Sound > Pen and Touch → select "Press and hold" → Settings, then the speed slider.
A stock installation fires the menu after a stationary hold of roughly 500 ms; the slider moves that in either direction, and builds differ. Two field cautions: after some Windows Update rounds the pen-and-touch press-and-hold entries have been reported missing (Microsoft's own Q&A carries the reports — the classic dialog is the fallback), and finger movement cancels the gesture no matter how long you meant to hold.
Browser-based visualizations can fail in the opposite direction, where an ordinary touch hold pops the context menu unwanted; CODESYS WebVisu long touch opening the right-click menu covers that side of the same setting.
The hold-duration test that rules timing out #
If you want the timing question closed with numbers before calling the vendor, run this matrix with a deliberately stationary finger:
| Hold time | Plain app (Notepad) | Failing application |
|---|---|---|
| 500 ms | menu opens | control drags |
| 1500 ms | menu opens, later | control drags |
The arithmetic: 1500 ms is 3 × 500 ms, an increase of 1000 ms — the duration tripled. Windows obeys the change: the menu still opens, just later. The application does not: an identical drag at both durations. The application is not waiting on the system gesture timer at all; it takes the contact stream and starts a drag on its own movement. Nothing you set on the panel changes that, so the decision is a correction inside the application.
The documented case and the correction that fixed it #
A Windows 10 operator console with a resistive touch screen showed exactly this split in KMotionCNC: press-and-hold opened menus in every other application, but in the G-code display the text box moved instead of the copy, paste and set-next-line menu appearing. The software's developer reproduced it and supplied a corrected executable identified for Version KMotion435c:
- Close the application.
- Copy the patched KMotionCNC.exe into C:\KMotion435c\KMotion\Release, replacing the file there.
- Restart and press-and-hold in the G-code area: the context menu with copy, paste and set next line is what must appear instead of the moving text box.
That retest passed on the affected console. The correction is identified for KMotion435c only — nothing extends it to other releases — so confirm the installed version and its folder before copying anything, and take the executable from the software's maintainer or its official distribution rather than a third-party download. Do the retest with the machine out of cycle, so a stray drag on a control area cannot command motion.
When the application has no correction yet #
- Report it with the evidence in the first sentence: press-and-hold opens the menu in Notepad and fails only in this application, at 500 ms and at 1500 ms. That rules out the panel outright and saves the vendor a day of driver chasing.
- Bridge with a mouse: a USB mouse restores right-click immediately and changes nothing else, while the touch surface keeps handling normal operation.
- The same layer split applies to PC HMI runtimes, where the vendor's gesture handling decides the outcome the same way — fixing the right-click gesture in an HMI runtime walks through that variant.
The decision for each outcome #
- Notepad works, one application drags at every duration: application fault. Get the vendor's correction for your exact version and accept it by the menu opening, not by the drag disappearing.
- No menu in any application: re-enable or speed up press-and-hold under Settings → Bluetooth & devices → Touch or in the Pen and Touch dialog, then retest Notepad.
- No touch cursor at all: digitizer link fault; treat it as a USB touch problem, not a gesture problem.
- Vendor has no fix for your version: run the mouse bridge, keep the report open with your test matrix attached, and retest any corrected executable with the machine idle.
Questions asked
Does press-and-hold right-click come from the touch driver?
No. The driver only reports contact positions; Windows itself synthesizes the right-click once a contact stays inside the movement tolerance for the configured duration. That is why a gesture that works in Notepad cannot be a driver fault — the driver has no idea which application is under your finger. Reinstalling or recalibrating it cannot make one application behave.
Where is the press-and-hold setting on a Windows panel?
Two places control it. The feature toggle sits under Settings, then Bluetooth & devices, then Touch. The duration slider is in the classic dialog: Control Panel, Hardware and Sound, Pen and Touch, select Press and hold, click Settings. If the Pen and Touch entries go missing after an update, that has been reported on Microsoft's own Q&A; the Settings toggle still controls the feature.
Why does a longer hold not fix the dragging application?
Because the application never waits for the gesture timer. Tripling the hold from 500 ms to 1500 ms changes when Windows fires the menu, but an application that reads the contact stream directly sees press-then-move and starts a drag on its own. Duration only matters to software that honors the system gesture, which is exactly what the failing application does not do.
How do I apply the correction in the documented case?
Confirm the installation is Version KMotion435c, close the application, copy the patched KMotionCNC.exe into C:\KMotion435c\KMotion\Release over the existing file, then restart and press-and-hold in the G-code area to confirm the copy, paste and set-next-line context menu opens. Take the executable from the software's maintainer or its official distribution, never a third-party download.
Can I keep the panel in service while waiting for a fix?
Yes. A USB mouse restores right-click immediately and changes nothing else on the station; the touch surface keeps working for normal operation. Do the acceptance retest of any patched executable with the machine out of cycle, so a stray drag on a control area cannot command motion while you are proving the menu.