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

[John Heil]

On Wed, 7 Jun 2006, John Heil wrote:

> Date: Wed, 7 Jun 2006 08:27:47 -0700 (PDT)
> From: John Heil <edadev at sc-software.com>
> To: R. Timothy Edwards <tim.edwards at multigig.com>
> Cc: xcircuit-dev at opencircuitdesign.com
> Subject: Re: [Xcircuit-dev] Mouse issues: Resolution...
>
> On Wed, 7 Jun 2006, R. Timothy Edwards wrote:
>
> > Date: Wed, 07 Jun 2006 07:32:22 -0700
> > From: R. Timothy Edwards <tim.edwards at multigig.com>
> > To: John Heil <edadev at sc-software.com>
> > Cc: xcircuit-dev at opencircuitdesign.com
> > Subject: Re: [Xcircuit-dev] Mouse issues: Resolution...
> >
> > 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.
>
> Cool...
>
> >
> > Unless you're working over a network, it sounds like fvwm2 is actively
> > disabling the HOLD function.  Either it's forcing the keyboard Mod2Mask
>
> In this case, no network. I have another CAD pkg for ME and the mouse
> buttons all work fine there and it too has a HOLD implementation so
> I'm not at suspecting fvwm2... yet...
>
> > (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,
>
> 150ms seems _way_ too fast for my pointer, an older Logitech 3 button
> TrackMan Marble (its buttons even 'feel' slow... perhaps accumulated
> grunge :) ).
>
> I'll try upping that time, first, & report back.
>

Nope... I tried 1000 and it still failed.

> > 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).

Bingo.
Mod2Mask was it... Mod5Mask worked perfectly... My orginal change
removed...

Button1 Hold to move, even works... :))

> >
> > 					---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               |
> > +--------------------------------+-------------------------------------+
> >
>

Thnx v much,
johnh

-
-----------------------------------------------------------------
John Heil
South Coast Software
Custom systems software, firmware and board bring up services
1-714-774-6952
johnhscs at sc-software.com
http://www.sc-software.com
-----------------------------------------------------------------