#13 Option to set the initial state of the click window button [no click]

someday
accepted
nobody
Interface (11)
general
5
2013-01-04
2010-12-03
georgn
No

if you have eviacam set to load at Windows startup and have the click window to appear as well, the initial state of the click window button [no click] is set to active. I think it would be better to change the initial state to inactive. it is better because booting up a computer doesn't necessarily mean, that the user the person who needs eviacam features.

What I want is this:
I want to be able to tell my nurses to switch on the computer and access certain files while I am not in the room. They usually don't understand what is going on when automated clicks happen. so the best solution would be to change the initial state of the click window button [no click] to inactive, so I only have to hover the mouse arrow over the button in order to activate it.

Discussion

  • Note that disabling the click generation ('no click' button) does not disable motion so, in the scenario you describe the nurse will find that the pointer moves.

    What about disabling pointer motion when the conventional mouse is used?

     
  • georgn
    georgn
    2011-03-31

    the problem is not the movement but the automated click. Even I myself happen to accidentally click after the program has been loaded.

    Disabling pointer motion while using a conventional mouse is a good idea for an option but it should not be a forced feature.

    I use eviacam and mouse simultaneously because when I am gaming positioning precision must be higher which I don't manage with eviacam if the easy stop zone is bigger than three pixels. If I don't set Easy stop to 5 I have huge difficulties not to make unwanted movements, though I'm able to control my head movements extremely exact. the lower easy stop is set, the more exact the mouse pointer can be controlled..for me it seems logical that a higher easy stop results in lower precision.

    My conclusion for this two things would be to include both of them as options.

     
  • Agreed. Queued these two configurable features for further development.

     
    • summary: dwell click not to be initially active --> Option to set the initial state of the click window button [no click]
    • status: open --> accepted
    • group: --> general
    • milestone: --> someday
     
  • Ticket name changed. I hope now it reflects better the exact purpose.

    For the feature "Disabling pointer motion while using a conventional mouse..." see:

    37 Pause on Mouse-Move,
    https://sourceforge.net/p/eviacam/feature-requests/37/