[Xcircuit-dev] Mouse issues: Resolution...

[R. Timothy Edwards]

Dear John,

> Turns out, 'HOLD' is always active ( Wm: FVWM2) no matter how quickly I
> tap mouse Button1.
> 
> Since there exists a move command tool button, I figured it was
> safe to just comment out the above line.

I didn't even think of that possibility.  I know of one person at
MultiGiG who had a similar problem with the HOLD function being delayed
across a network and making it difficult to work.  I added a menu option
"Options-->Allow Hold Mode" that can be turned off to create the same
behavior you generated.  For future reference, you can avoid patching
every version of xcircuit by having a .xcircuitrc file with the command
"config hold false", which will disable it permanently.

Unless you're working over a network, it sounds like fvwm2 is actively
disabling the HOLD function.  Either it's forcing the keyboard Mod2Mask
(which I used for HOLD because it isn't usually mapped to anything),
or else the timer is not working properly.  You could also try to
change PRESSTIME (xcircuit.h line 993) to something larger, like 500
or 1000, just to see if 150 milliseconds is just too fast.  Otherwise,
if it's the key mask that's the problem, you might fix it by changing
Mod2Mask to something less likely to be used, like Mod5Mask, in all
occurrences (3 times in keybindings.c or once in events.c).

					---Tim

+--------------------------------+-------------------------------------+
| Dr. R. Timothy Edwards (Tim)   | email: tim.edwards at multigig.com     |
| MultiGiG, Inc.                 | web:   http://www.multigig.com      |
| 100 Enterprise Way, Suite A-3  | phone: (831) 621-3283               |
| Scotts Valley, CA 95066        | cell:  (240) 401-0616               |
+--------------------------------+-------------------------------------+