Windows Version of Dragsens

UPDATE: Download the latest version from the main project page. There is also a console-based version of this utility that’s more suitable for system administrators.

In response to a comment on the previous version of the drag sensitivity utility, I’ve created a new version of the utility that includes a graphical interface and a means of testing the drag settings in the interface.

WinDragSens Interface

This version also maintains all of the command-line parameters of the previous version so that it may still be used from scripts or batch files.

You may download the executable here:

http://www.parkscomputing.com/code/WinDragSens.zip
(MD5 hash: CC1680ED81730AA73F70BCD21F0A6CB1)

If you’d like to examine or modify the source code or build your own executable rather than relying on the executable above, you may download the Visual Studio 2013 project and source here:

http://www.parkscomputing.com/code/WinDragSens_src.zip
(MD5 hash: 3D1AF2688F9560D90CAE8FD266F48915)

Please let me know if you encounter any problems or have any questions.

12 comments on “Windows Version of Dragsens
  1. Mark says:

    Hi,
    I LOVE dragsens… I work in schools where ever since they started using lots of netbooks/laptops with touchpads folders are dragged and dropped all over the place. This has curbed that except for the occasional know-it-all in the class who just moves things around for ‘fun’… that I can deal with.
    Just wondering if in a future update you could add an option to the cmd line version that would return the Horiz and Vert sensitivity
    [aka:
    C:\>drangsens /q
    might result in:
    C:\>H:4 V:4
    -or-
    C:\>4,4
    or something similar that could be parsed in a script) to the command line so that I could script it in part of the login and look for any (new) machines that are not in an acceptable range and then fix them. The alternative is to either use the Windows version on hundreds of them or change them all at each login. Just a thought.
    Again thank you for what you have done.
    Mark

    • Thank you, Mark. I’m happy that you’ve found it useful.

      That’s a good idea you have for returning the existing sensitivity values. I’ll see if I can put that into the command-line version of the tool. It should be a simple change.

      Thanks again,
      PMP

    • Mark,

      What about this? The /D parameter, by itself, will display the current settings:

      C:\>dragsens /d
      Current settings:
      X=4, Y=4

      When combined with the existing /X and /Y parameters, it will also display the new settings:

      C:\>dragsens /d /x 20 /y 20
      Current settings:
      X=4, Y=4

      New settings:
      X=20, Y=20

      Would that work for you?

      PMP

  2. Niall says:

    Hi, will this just affect drag and drop behavior in windows explorer or will it affect dragging and dropping objects in all application? E.g. moving shapes in office programs.

    • Hi, Niall,

      It will affect all drag operations in Windows, except for the odd application that might try to bypass the Windows API and do its own drag detection. That should be rare, however.

      Thanks,
      PMP

  3. Laz says:

    The version on line is being Identified as a Trojan, is there a clean copy? Trojan.Gen.SMH

  4. Thank you for that program!
    It is in use network wide with “48” in some company LANs now, preventing the accidental “move one folder into another on a network drive” in most cases. Lowers the number of “lost data” phone calls which are just moves files or directories.
    I know, 48 sounds high, but it is not as high as you may think.

  5. Steve McNeal says:

    Windows 10 Pro 64-Bit. Downloaded WinDragSens.Zip and Extracted WinDragSens.Exe (1.1.0.1 279Kb 1/23/2016) and When Double Clicked Nothing Happens – Also Tried Right Click with Run as Admin. with Same Results?

  6. Patric says:

    Thank you, thank you so much.
    Finally ending the drag copy problem.

  7. Kmov says:

    Great work, made my day! Thanks for the creation!

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*