Alex Perry writes:
I like the concept of the mice.xml file, but am not really
comfortable about having the implied modal state hidden in there.
Can we break it out, so that mouse, joystick and keyboard events
can be conditional on state variables ?
Thanks for looking at the code.
There
In fact, I had originally implemented mice.xml that way (as you
suggested in your example), but it seemed very verbose
Much of the verbosity is because we're attaching the conditional
to every occurrence of the combination of mode and of input event.
Perhaps we should have the modifier set a
David Megginson wrote:
Alex Perry writes:
I like the concept of the mice.xml file, but am not really
comfortable about having the implied modal state hidden in there.
Can we break it out, so that mouse, joystick and keyboard events
can be conditional on state variables ?
Thanks
Erik Hofman writes:
What i *realy* like about the new code is the way the mouse pointer
moves from one side of the screen to the other side when clipping to
the borders.
Thanks.
What I don't like is the fact that, when changing pointers, the
view stays fixed to the last position.
What I don't like is the fact that, when changing pointers, the view
stays fixed to the last position. I'm realy lost at where I'm looking at
and where I should expect the front of the plane.
I would suggest that the view direction would be reset to straight ahead
when switching modes.
David Megginson writes:
It isn't hard to change the file to make the view snap back when you
leave mouse-view mode -- we'll just have to choose a default.
Personally, I prefer to have the view direction stay put when I leave
mouse view mode, especially when using the 3D cockpit. What does
Alex Perry writes:
What I don't like is the fact that, when changing pointers, the view
stays fixed to the last position. I'm realy lost at where I'm looking at
and where I should expect the front of the plane.
I would suggest that the view direction would be reset to straight ahead
when
Curtis L. Olson writes:
I finally got a chance to try the new 3d cockpit interior and it is
a very good start. It's pretty awkward trying to fly with the
keyboard and pan the view with the mouse since I'm used to flying
with the mouse.
In that case, consider rebinding the arrow keys to
Norman Vine writes:
This was IMHO necessary for the MOUSE_YOKE mode and
very useful for the other modes. Some of this was compile time
configurable, FWIW this was fairly tricky to get right at first but
is fairly straight forward once you figure out what you need.
ie when cycling
David Megginson wrote:
Curtis L. Olson writes:
I finally got a chance to try the new 3d cockpit interior and it is
a very good start. It's pretty awkward trying to fly with the
keyboard and pan the view with the mouse since I'm used to flying
with the mouse.
In that case,
David Megginson writes:
Norman Vine writes:
This was IMHO necessary for the MOUSE_YOKE mode and
very useful for the other modes. Some of this was compile time
configurable, FWIW this was fairly tricky to get right at first but
is fairly straight forward once you figure out what you
David Megginson wrote:
Erik Hofman writes:
What I don't like is the fact that, when changing pointers, the
view stays fixed to the last position. I'm realy lost at where I'm
looking at and where I should expect the front of the plane. I
would suggest that the view direction would
Alex Perry wrote:
On the 2D panel and the HUD, we already have visual control
feedback. On the 3D panel, we can replace the scale indicators with
a moving yoke.
Right, but in both 2D and 3D mode, the panel/HUD isn't guaranteed to
be on the screen. They both disappear if you move your
Andy Ross writes:
The issue of visual feedback is a good point. I wonder if the best
solution would be to turn off the mouse cursor entirely and use the
control indicators on the panel or hud?
I've been thinking along the same lines. We need some kind of visual
feedback, though, so that
Alex Perry writes:
On the 2D panel and the HUD, we already have visual control feedback.
On the 3D panel, we can replace the scale indicators with a moving yoke.
Yes, that's coming very soon.
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
I like the concept of the mice.xml file, but am not really comfortable about
having the implied modal state hidden in there. Can we break it out, so that
mouse, joystick and keyboard events can be conditional on state variables ?
mouse n=0
button n=2
binding
conditional
16 matches
Mail list logo
