1.3 and other Versions

Hi!
I would recommend something like a public wishlist and in which version
the requested feature will be implemented or if it is rejected. E.G., I would
like to see the following things in SDL:

  1. Access to the screens front buffer in double buffering (BTW: Sam, do you
    remember, that you wanted to do a hack for demonstations? I have finished
    the preparaions this weekend and only have to bring the changes of SDL in…)
  2. A platform independent function to gain the current position of the cursor
    without the mouse motion event to prevent time lags. Something like SDL_GetCursorPos.
  3. OpenGL on surfaces. I have discovered, that this is possible in Win32 and
    under MESA, so other implementations definitly should have this feature, too.

Regards,
Andreas Podgurski

  1. A platform independent function to gain the current position of the cursor
    without the mouse motion event to prevent time lags. Something like SDL_GetCursorPos.

SDL_GetMouseState()

Along with SDL_PumpEvents() for immediate gratifacation.On Tue, Dec 19, 2000 at 12:30:00PM +0100, Mattias Engdeg?rd wrote:

  1. A platform independent function to gain the current position of the cursor
    without the mouse motion event to prevent time lags. Something like SDL_GetCursorPos.

SDL_GetMouseState()


Martin

Bother, said Pooh, as he built a glove with knives for fingers.

  1. A platform independent function to gain the current position of the cursor
    without the mouse motion event to prevent time lags. Something like SDL_GetCursorPos.

SDL_GetMouseState()

Along with SDL_PumpEvents() for immediate gratifacation.
But doesn’t that perform some things with the other Events, too? To be true, I havn’t looked
that deep in detail, because I don’t have the current sources of my project here, so sorry, if
it really does that. But if I understand the thing correct, it only retrieves the coordinates from
the Event queue, so they are “heavy” time lagged. If I am using windows GetCursorPos,
they are directly read (Indicated by the fact, that no event function is needed before ;-). True,
SDL_GetCursorPos only needs to be adepted for that.

Regards,
Andreas PodgurskiOn Tue, 19 Dec 2000 13:20:47 +0000, Martin Donlon wrote:

On Tue, Dec 19, 2000 at 12:30:00PM +0100, Mattias Engdeg?rd wrote:

The way I see it, I could be wrong on this point. SDL_GetMouseState will
return the most upto date info on the mouse. If you read through the entire
event queue, the last motion event you encountered would contain the same info
that SDL_GetMouseState gives you. SDL_GetCursorPos would simply call
SDL_PumpEvents and SDL_GetMouseState.

However, the arguement is largely academic. The amount of lag is tiny and not
really worth considering - calling SDL_PumpEvents and SDL_GetMouseState will
give you the position on the mouse as accurately as the operating system can
determine. Hell, using the event queue is just as accurate.On Tue, Dec 19, 2000 at 07:47:15PM +0100, Andreas Podgurski wrote:

Along with SDL_PumpEvents() for immediate gratifacation.
But doesn’t that perform some things with the other Events, too? To be true, I havn’t looked
that deep in detail, because I don’t have the current sources of my project here, so sorry, if
it really does that. But if I understand the thing correct, it only retrieves the coordinates from
the Event queue, so they are “heavy” time lagged. If I am using windows GetCursorPos,
they are directly read (Indicated by the fact, that no event function is needed before ;-). True,
SDL_GetCursorPos only needs to be adepted for that.

Martin

Bother! said Pooh as he twitted his moderator.