Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 May 2002 08:43:40 -0700
From:      jehova <tornadox@telnor.net>
To:        "Brian T.Schellenberger" <bts@babbleon.org>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: mouse code kernel
Message-ID:  <0GVH00D74POYXG@email.telnor.net>
In-Reply-To: <20020502145015.9A979BB29@i8k.babbleon.org>
References:  <0GVG00A9UVVBRZ@email.telnor.net> <0GVH00C5ANR0N0@email.telnor.net> <20020502145015.9A979BB29@i8k.babbleon.org>

next in thread | previous in thread | raw e-mail | index | archive | help
El Jue 02 May 2002 07:50, escribió:
> Oh, sorry, I forgot.
>
> You'll have to disable moused as well.
>
> By the way, do regular console windows have the same problem
> with the mouse when you mark fast?  This might be interesting
> input . . .

It works!!! thanks Brian, well now i dont have mouse enabled on 
console but in this machine i need X capabilities (my wife is
graphic designer, she says hi and thank you).

where can i find info about this solution? Ok, i follow your 
instructions, but i want to learn what i am doing. 


> | > |
> | > | when i draw a box (rectangle tool on gimp), if i do it
> | > | quite slowly, i start my draw on place where i click and
> | > | drag mouse pointer works fine. But if click and drag for
> | > | draw a box faster my box is draw  away  from the place
> | > | where it supose to be, something like one  inch (depends
> | > | on speed: faster more desplaced, slower draw near. if i
> | > | want select a text (for example for  cut and paste), slow
> | > | or medium velocity works well, but if i speed up: start
> | > | selection 2,3 4 or 6 characters later. this behavior
> | > | happens with with TWM, KDE and XFCE and with every
> | > | drawing program i've been tried (gimp, xpaint or
> | > | whatever).
> | > |
> | > | i've been discard Xfree because versions 3.3.6, 4.1 and
> | > | 4.2 do same on freebsd 4.4 and 4.5. nothing of this
> | > | happen on linux this is why i think maybe is a kernel
> | > | related issue.
> | >
> | > If you are running X anyway, then the simplest solution is
> | > probably just to bypass the kernel mouse code entirely.
> | >
> | > Just change the mouse in your XF86Config from /dev/mouse to
> | > dev//psm0 (for a PS/2 mouse, the most likely choice) or
> | > whatever your real underlying mouse device is and restart
> | > X.
> | >
> | > Then you won't be using the the kernel-based "sysmouse"
> | > driver at all, just X mouse support.
> |
> | i have 'moused' enabled on console with  dev/psm0, then on
> | XF86Config change device to dev/psm0, it did't work i need to
> | add AllowMouseOpenFail to startx and neither works mouse. why
> | change for bypass kernel mouse code device port? there are
> | other ways to bypass?(!?)


Thank you very much,
see you on line 
                                _ __ ___ ____  ___ ___ ___  __
    Jehova                           _ __ ___ | _ ) __|   \/  \
    tornadox@telnor.net                  _ __ | _ \._ \ |) |  |
    FreeBSD!!!                              _ |___/___/___/ \/ 
           "Extracting Wisdom from Sinful...                ()
           ...Searching State of Purity."







To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0GVH00D74POYXG>