#42 Mouseclick to short for some programs

None
pending
nobody
None
windows
5
2015-01-07
2013-04-16
georgn
No

Some programs or games do not recognize the clicks coming from Enable Viacam. Some of the programs are FL-Studio, Dungeons of Dredmor, Jagged Alliance - Back in Action, Jamestown, Torchlight II, Bastion, Project Zomboid, and others of which I have forgotten to write down in my notes.

I'm quite sure that this has something to do with the length of the pause between mousedown and mouseup of the click, because when I use the drag click in these programs/games, the clicks are recognized correctly but it is not very practical a woraround.

Discussion

  • georgn
    georgn
    2013-04-16

    Windows 7 Professional 32 Bit.

     
  • Try the attached AutoHotKey [1] script which introduces a delay between mousedown and mouseup. You could edit the script to adjust the delay. Try and let me known. If it works I'll add this feature to eviacam.

    [1] http://www.autohotkey.com/

     
    Attachments
  • georgn
    georgn
    2013-04-16

    the script works.
    I tested it in the alpha demo of Underrail which didn't recognize the standard click of Eviacam. With the AHK-Script it works.
    By the way, click-drag doesn't work anymore with the script running.

     
  • georgn
    georgn
    2013-04-17

    Today I noticed that with the AHK-Script running the shift-key of the Windows 7 On-Screen-Keyboard isn't working anymore either, at least when trying to mark words in an input box or a texteditor with shift+pos1/end/cursor.

     
  • Attached is another script which kills all AutoHotKey instances. You can use both as a workaround until this feature is implemented in eviacam. I.e. use the former for those applications that need the pause between mouse actions and the later to close AutoHotKey.

     
    Attachments
    • status: open --> pending
    • Milestones: -->
     
  • georgn
    georgn
    2013-10-29

    Well, this 2ms version works occasionally. That means about one out of 10 or more clicks is recognized. I have the hunch that the two milliseconds might be swallowed by some stuff that's going on while Windows is doing something in the background. Single clicks can be quite lengthy. Perhaps we could try something close to ten milliseconds. I'm not sure if it will be a good value but maybe it is better. If you want to test it yourself you could try to install the demo of the game Primordia. It doesn't recognize the standard click of Enable Viacam.

    Thank you for addressing the issue. Please forgive me for not answering earlier.

     
  • Since v1.7.2 there is an option in the advanced tab which allows to set the delay between mouse down and up events. Please, check whether this fixes the problem.

     
  • georgn
    georgn
    2014-05-06

    great. problem fixed. thank you!

     
  • georgn
    georgn
    2015-01-07

    Well, it seems that there are still some programs that require an even longer delay between mouse up and mouse down. The option you added is very good but it only allows for the addition of a maximum of 10 ms. I'd suggest to make that 30 to 50 ms. And it might be usefull to use the same value for all buttons. I don't know if it's already the case.

     
  • OK. Range enlarged up to 50ms

    commit c8e87c7bf60bc1304d23f3b296717acc59b5c224

    In a few days I plan to release a new version.