On 31/12/2008, at 10:55 AM, "Tristam MacDonald" <[email protected]> wrote:
> On Tue, Dec 30, 2008 at 7:30 PM, Alex Holkner > <[email protected]> wrote: > > On 12/31/08, __doc__ <[email protected]> wrote: > > > > The on_mouse_motion event reports the mouse position in pixels. > > > > I think this is suboptimal in the context of pointing your viewport > > with the mouse for these reasons: > > > > 1) The Operating system applies algorithms on the mouse position > like > > acceleration you might not want on your 3d view > > 2) The resolution is per pixel only, and if you want to scale > > sensitivity up in your game you'll have to multiply the pixel delta > > which leads to undesirable jumping of perspective. > > 3) Some mice have a higher time/dpi resolution then others, > however if > > all input gets downsampled to pixel resolution, then it is > impossible > > to make use of better mice. > > 4) Movement of the cursor is relative to screen resolution. If you > > switch between fullscreen and windowed and there are different > > resolutions, the mouse will have different sensitivities (because > one > > will yield more screen delta covered per moved mouse distance > then the > > other) > > > > I think DirectInput was able to read the mouse buffers out > without the > > values getting mangled trough the window manager. > > > > Is it possible (on linux) to get the mouse buffer values before > they > > are downsampled and recomputed to map to screen pixel coordinates? > > This functionality is (sort of) available in pyglet 1.2's pyglet.input > module. I say sort of, because pyglet provides access to all HID > devices it can see, which on Linux does include the hardware mouse, > but it won't tell you which device is a mouse (you'll need to find a > heuristic for this yourself). > > Check out trunk and look at examples/show_input.py to see if it's > reporting the values you need. > > Alex. > > Would it make sense to implement a function in pyglet.input, which > attempts to detect the primary pointing device? There's not much sense in that -- such a device is usually called the virtual system mouse, and is exposed by the Window mouse events. Alex. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
