Whenever the mouse selector pointer rests on a file or folder icon, Windows generates an automatic delete action, and the deleted files can't be found in the Recycle bin.Īnyhow, left mouse click = delete and it brings big data loss trouble, which makes users frustrating.
Or if the folder has files inside, Windows will ask for your confirmation to delete it many times until you really do.
Clicking on an empty folder will delete it.
Instead, they get deleted straightly without asking.
Programs, shortcuts, files, or folders won't open on double left-click as normal.
When you encounter this problem, the details may be as follows. Incomplete installation of programs, problematic Windows OS, outdated mouse driver, virus attacks, and false registry change on your system are the main reasons for this to occur. It has been reported by many users on Windows 10. Left-click behavior on a mouse causes a deletion. Which returns TRUE if the mouse buttons have been swapped.PAGE CONTENT: Things to do first: Recover left-click deleted files Fix left-click causes file deletion problem Problem: Files Get Deleted Automatically When Left-Click You can determine the system's current mapping of physical mouse buttons to logical mouse buttons by calling GetSystemMetrics(SM_SWAPBUTTON), For example, the call GetAsyncKeyState(VK_LBUTTON) always returns the state of the left physical mouse button, regardless of whether it is mapped to the left or right logical mouse button. However, it checks on the state of the physical mouse buttons, not on the logical mouse buttons that the physical buttons are mapped to. The GetAsyncKeyState function works with mouse buttons. Use the GetAsyncKeyState function to retrieve that information.Īlso note the GetAsyncKeyState() documentation states: The status does not reflect the interrupt-level state associated with the hardware. The key status returned from this function changes as a thread reads key messages from its message queue. This is very clearly stated in the documentation: But your loop does not process any messages at all, which is why GetKeyState() does not work. GetKeyState() relies on the keyboard state of the calling thread, which is updated when the calling thread processes keyboard window messages, like WM_KEYDOWN and WM_KEYUP.
0 kommentar(er)
