Hello,
attached mice;
however it might be convenient to have an api that returns the number of
mice that are pressing a button.
This comes in handy for the iphone for example where you might want to
assign a two fingers touch an action, without having to rely on the main
loop.
comments, critics, suggestions?
Vittoriofrom my understandings the SDL_GetNumMice() returns the total number of
I think a true multi-touch API would be a great thing to add for SDL
1.3. I suspect that multi-touch devices are going to explode in the
next year or two.
Any volunteers to break this ground? :)On Mon, Oct 19, 2009 at 4:04 PM, Vittorio G. <vitto.giova at yahoo.it> wrote:
Hello,
from my understandings the SDL_GetNumMice() returns the total number of
attached mice;
however it might be convenient to have an api that returns the number of
mice that are pressing a button.
This comes in handy for the iphone for example where you might want to
assign a two fingers touch an action, without having to rely on the main
loop.
comments, critics, suggestions?
Vittorio
Charles de Gaulle ?- “The better I get to know men, the more I find myself
loving dogs.”
-bill!On Wed, Oct 21, 2009 at 09:48:13PM -0700, Sam Lantinga wrote:
I think a true multi-touch API would be a great thing to add for SDL
1.3. I suspect that multi-touch devices are going to explode in the
next year or two.
That might make for a good GSoC project for next summer?
-scottmcOn Thu, Oct 22, 2009 at 4:48 AM, Sam Lantinga wrote:
I think a true multi-touch API would be a great thing to add for SDL
1.3. I suspect that multi-touch devices are going to explode in the
next year or two.
I think a true multi-touch API would be a great thing to add for SDL
1.3. ?I suspect that multi-touch devices are going to explode in the
next year or two.
Any volunteers to break this ground?
If I can actually get around to it, and it manages to find it’s way
into SDL proper, the control level API I keep talking about, where a
device may create and destroy it’s controls, would make this
relatively simple… A multi-touch device would create a pointer when
you touch the screen and destroy it (or mark it for cleanup), when you
stop touching the screen.
It would also mean you have a way of keeping various mouses and
multi-touch devices separate, which would be a problem if you’re just
creating and destroying SDL mice.
i’m willing to help in someway, either beta testing or developing (though i
have no knowledge on sdl internals)
bye
vittorioOn Thu, Oct 22, 2009 at 8:22 PM, Kenneth Bull wrote:
2009/10/22 Sam Lantinga :
I think a true multi-touch API would be a great thing to add for SDL
1.3. I suspect that multi-touch devices are going to explode in the
next year or two.
Any volunteers to break this ground?
If I can actually get around to it, and it manages to find it’s way
into SDL proper, the control level API I keep talking about, where a
device may create and destroy it’s controls, would make this
relatively simple… A multi-touch device would create a pointer when
you touch the screen and destroy it (or mark it for cleanup), when you
stop touching the screen.
It would also mean you have a way of keeping various mouses and
multi-touch devices separate, which would be a problem if you’re just
creating and destroying SDL mice.
The multiple mouse API is designed for multiple physical and
independent input devices. The current hack to map multi-touch to
mice on iPhone is something I expect to go away once we had a true
gesture API.On Thu, Oct 22, 2009 at 11:22 AM, Kenneth Bull wrote:
2009/10/22 Sam Lantinga <@slouken>:
I think a true multi-touch API would be a great thing to add for SDL
1.3. ?I suspect that multi-touch devices are going to explode in the
next year or two.
Any volunteers to break this ground?
If I can actually get around to it, and it manages to find it’s way
into SDL proper, the control level API I keep talking about, where a
device may create and destroy it’s controls, would make this
relatively simple… A multi-touch device would create a pointer when
you touch the screen and destroy it (or mark it for cleanup), when you
stop touching the screen.
It would also mean you have a way of keeping various mouses and
multi-touch devices separate, which would be a problem if you’re just
creating and destroying SDL mice.
