Erik Hofman writes:
>
>David Megginson wrote:
>.
>>
>> What does everyone else prefer -- should the mouse get stuck on the
>> window edges in constrained mode, or should it wrap around?
>I have no
>> strong preference either way. There are good arguments in favour of
>> both: with wrap-around,
David Megginson wrote:
.
>
> What does everyone else prefer -- should the mouse get stuck on the
> window edges in constrained mode, or should it wrap around? I have no
> strong preference either way. There are good arguments in favour of
> both: with wrap-around, you still see cursor movement
David Megginson writes:
>
>What does everyone else prefer -- should the mouse get stuck on the
>window edges in constrained mode, or should it wrap around? I have no
>strong preference either way. There are good arguments in favour of
>both: with wrap-around, you still see cursor movement while
Norman Vine <[EMAIL PROTECTED]> said:
>
> The default use to be wrap in horizontal and not be able to go pass
> straight-up or down. I am assuming that this behaviour was generally
> acceptable as there was VERY little < or none > discussion as to it's
> short comings on the list
>
Yes, actua
Norman Vine writes:
> > if (mode.constrained) {
> >bool need_warp = false;
> >if (x <= 0) {
> > x = xsize - 2;
> > need_warp = true;
> >} else if (x >= (xsize-1)) {
> > x = 0;
>
> should be x = 1;
Oops -- I missed this one. It looks like I guessed Norm
Norman Vine writes:
> Here is a start at a 'positionable' mouse that I find makes the new
> mouse MUCH easier to deal with when switching modes and a
> doMouseMotion() that is MUCH closer to what we had
Great, thanks.
> if (mode != m.current_mode) {
> m.current_mode = mode;
> gl
Norman Vine wrote:
>
>and a doMouseMotion()
>that is MUCH closer to what we had
OOOPS ...
>void
>FGInput::doMouseMotion (int x, int y)
>{
> // Constrain the mouse if requested
> if (mode.constrained) {
>bool need_warp = false;
>if (x <= 0) {
> x = xs
Norman Vine wrote:
>
>David Megginson writes:
>>
>>I think that we're ready to switch over to the configurable mouse now
>>as the default, and to remove the old src/GUI/mouse.cxx code.
>>
>
>Hmm - I just updated from CVS and now clicking the right mouse button
>has no effect what so ever !
Oops
David Megginson writes:
>
>I think that we're ready to switch over to the configurable mouse now
>as the default, and to remove the old src/GUI/mouse.cxx code.
>
>There are still a couple of open questions (i.e. mouse cursor-position
>feedback) and one missing minor feature (automatic menu hiding)
