I have a touch screen computer with Windows 7 and I would like to disable the multi-touch gesture :
But even if I disable it and apply the changes, when I reopen the window, the option is enabled again...
Any idea where I can disable it for good ? (maybe in the registry...)
Up: still have the problem.
How to disable "multi-touch gestures and inking"
Run \Windows\System32\regedt32 as Administrator
Navigate to HKEY_USERS
Find entry that starts with S-1-5-21-xxxxxxxx
Note there might be a few GUIDS that starts with S-1-5-21.
You need the one that you can drill to
S-1-5-21xx\Software\Microsoft\Wisp
Under Wisp key there should be keys like Pen, Touch,
to indicate you are in the right location
Under Wisp key add additional key MultiTouch
Go inside MultiTouch key and create DWORD
MultiTouchEnabled set to 0
Reboot
Related
ISSUE:
On a touch panel with no keyboard, my QT C++/QML app running on Windows 10 IOT has the fullscreen GUI "frozen", when the monitor turns on (after the user has triggered the touchscreen), after it has timed-out earlier and turned off due to power settings. Mouse cursor still updates.
The QML GUI has "flags: Qt.FramelessWindowHint | Qt.Window"; I do not want to add "Qt.WindowStaysOnTopHint" as it will block the control panel window when it is open from the app. The program is verified to be still running, only the GUI has frozen from the point in time when the screen turned off.
TEMPORARY RESOLUTION:
The only way to "unfreeze" the fullscreen GUI is to connect a keyboard & press the Windows key to show-hide the start menu, or do it programmatically with a manual QML button placed at a known position or on detection of monitor WM_POWERBROADCAST messages.
When the app is not fullscreen, the freezing doesn't seem to be happening.
Is this due to some missing WM_MESSAGES (e.g. WM_PAINT, WM_ACTIVATE, etc) sent by the OS to the app when it is fullscreen, or when the start menu button is pressed?
Can the app-fullscreen-freezing on monitor-turn-back-on be rectified by the app programmatically sending a sequence of WM_MESSAGES to itself, but not the Win button keypress (as the normal user is not supposed to access the OS or see anything related to the OS when the app is running)?
I tried using winAPI SetForegroundWindow() function...?
:-( Fast forward a few days...
With further testing, it seems that using SetForegroundWindow() alone is not consistent/reliable. Sometimes it works, sometimes it doesn't.
The most reliable that works 99.999% of the time is still the VK_LWIN keypress sent by the app. But, as mentioned before, the app user is not supposed to see the start-menu appearing then disappearing. Best if the behavior of the VK_LWIN keypress could be duplicated to the app without seeing the start-menu...
I often find myself tapping the Win key by mistake, how to disable it when it's the only key being pressed using AutoHotkey?
In other words, tapping Win shouldn't bring up the start menu, but the Win key combination shortcuts should still work, e.g. pressing Win+X should open the quick link menu.
Quote from #MenuMaskKey:
The Start Menu (or the active window's menu bar) can be suppressed by sending any keystroke. The following example disables the ability for the left Win to activate the Start Menu, while still allowing its use as a modifier:
~LWin::Send {Blind}{vkE8}
Quote from Blind mode:
The Blind mode can be enabled with {Blind}, which gives the script more control by disabling several things that are normally done automatically to make things work as expected.
~LWin::Send {vkE8} may not work in some cases without {Blind}.
My C++ game allows users to hold down the shift key for a speed boost, but after 8 seconds this causes an annoying dialog to pop up on a fresh Windows 10 machine ("Do you want to turn on Filter Keys?"). Is there a way to disable this programmatically while my game is running?
I suggest you could refer to the Doc:Disabling Shortcut Keys in Games
To avoid these issues, you should disable these keys when running in full-screen mode, and either enable the keys back to their default handlers when running in windowed mode or exit the application.
To turn off these shortcuts:
1,Capture the current accessibility settings before disabling them.
2,Disable the accessibility shortcut when the application goes into full-screen mode if the accessibility feature is off.
3,Restore the accessibility settings when the application goes into windowed mode or exits.
You could try to use SystemParametersInfo to Get and Set System Information.
I was searching on internet how to enable "auto-switch" or "auto-raise" window that has flashing button on taskbar in Windows 7,
and all I can find is how to disable that! I need just opposit, to enable that so i looked at that answers and found registry key
ForegroundLockTimeout. It is set to 200000ms by default i think, so i set it to 1ms, but that doesn't affect anything after Windows XP I guess..
I found that it used to be possible to enable auto switching in Tweak UI from Microsoft, but that doesn't seems to work on Win 7 either.
I tried to program that in Delphi and I can set window on top with SetForegroundWindow, but i can't detect which windows need attention - are flashing.
It is even possible to detect foreground window with GetForegroundWindow, but not window that is flashing so i could set it on top.
So my question is, is it possible in delphi to get hwnd of that window that needs focus in background?
I would like to completely remove the Windows 7 taskbar, including tray and start-button, so that the user can not reactivate it by pressing the Windows-key on the keyboard. however, all other explorer functionality (i.e. starting an explorer Window using Windows+E) should remain.
Is it possible to permanently hide the complete taskbar? Maybe there are some registry values on could change in order to make that behaviour selectable using a powershell script?
Thanks a lot
Here be my solution (it hides rather than replaces or removes the native taskbar - this allows it to work with programs that have a dependency on the native taskbar, such as display fusions taskbar).
disable-taskbar-always-top
Still to solve: [HALF SOLVED]
Eliminate the stupid line that auto-hide leaves with some maximized applications, such as Google Chrome
HALF SOLUTION -
If you move the taskbar to the left or right edge prior to doing the above steps, you don't get the stupid auto-hide line at the top or bottom of Google Chrome. Since the native taskbar is not mouse sensitive anymore, it won't impact your use of hot corners, or multi monitors (for instance I have the native taskbar on the left of my middle monitor, and it does not popup when moving between monitors using the steps in this post).
Okay, I think I have finally - finally - got a workaround that:
Keeps the native Windows 7/8 taskbar hidden for your session (you do have a couple of steps you need to do on start-up each time, or if you manually un-hide the taskbar).
Prevents the native Windows 7/8 taskbar from opening with popups or programs seeking attention (flashing taskbar thing).
Prevents the native taskbar from being mouse sensitive (i.e. despite auto-hide, it will not appear when you mouse over the hidden taskbar anymore).
Allows you to use the screen area that is occupied by the native taskbar (this is the problem of not combining Taskbar-Hide with the autohide setting; you can't use that screen real-estate).
Allows you to run alternative taskbars that are dependent on keeping the native taskbar functional (for instance Dislay Fusions Multi-Monitor Taskbar + [Settings >> Advanced Settings ?> 'Show On All Montiors'])
One Time Steps:
1) Download and run this registry edit to prevent balloon notification popups from the native taskbar/system tray:
Notifications - Enable or Disable Message Balloons - Windows 7 Help Forums
(You can open this in notepad to see what changes it will make prior to installing it, if you want).
2) Download and run Taskbar-Hide from here:
Hide Taskbar: Hide Taskbar in Windows 8 | 7 with a hotkey
3) Set the taskbar to auto-hide
Optional:
3) B) Add a shortcut to Taskbar-Hide.exe in your startup folder, to have it launch automatically with windows on startup (you still need to use the Ctrl+Esc hotkeys to activate the functions of taskbar-hide - though you could also script this if you were really keen).
Startup Folder:
C:\Users{User Name}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
Steps to hide taskbar after each start-up or manually un-hiding using Taskbar-Hide
4) Make sure Taskbar-Hide is running.
5) Make sure the taskbar is in its auto-hide state (i.e. you'll have to look at any programs that are currently seeking attention).
6) Once the taskbar is 'auto-hidden', press the hotkeys for Taskbar-Hide (Ctrl+Esc)
[This should mean that the native taskbar area is no longer sensitive to mouse activity]
One way is to replace the explorer shell with your own shell. This is the a common method done in Windows 7 Embedded.
In older versions of Windows (such as XP) it was possible to specifiy a shell for each user via regedit. I am not sure this is easily possible in Windows 7.
See https://superuser.com/questions/352865/how-do-i-change-the-windows-shell-for-only-one-user
Make an empty exe file and use it as the file to use in your "Custom User Interface" group policy. Additional information here.
I have found another solution that works nearly perfect for me, by just hiding the Taskbar and the Start button by simply sending both the WM_HIDE message:
Handle = FindWindow("Shell_TrayWnd", "");
...
ShowWindow(Handle, SW_SHOW);
The only problem I have with that solution is that the taskbar is not hidden permanently, i.e. as soon as one element is activated that does not have the focus, which on the taskbar leads to the item flashing in yellow, the taskbar gets visible again.
I'm not sure if there is a way to prevent Windows from re-enabling the visible flag of the taskbar in some way, or a method to hook to the SW_SHOW in C# though.