|
Size: 1886
Comment: add search exclusions for SG pages
|
Size: 1847
Comment: cached searchs
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| ||<tablewidth="100%" style="color: #FF0000;" :> DRAFT|| | |
| Line 30: | Line 29: |
| ##<<FullSearch(category:CategoryEnum CategoryMouse -SGEnumerations)>> | ##<<FullSearchCached(category:CategoryEnum CategoryMouse -SGEnumerations)>> |
| Line 33: | Line 32: |
| ##<<FullSearch(category:CategoryStruct CategoryMouse -SGStructures)>> | ##<<FullSearchCached(category:CategoryStruct CategoryMouse -SGStructures)>> |
| Line 36: | Line 35: |
| <<FullSearch(category:CategoryMouse -CategoryEnum -CategoryStruct -SGFunctions)>> | <<FullSearchCached(category:CategoryMouse -CategoryEnum -CategoryStruct -SGFunctions)>> |
Mouse Support
Include File(s): SDL_mouse.h
green
Contents
Introduction
This category contains functions for handling inputs from mice and other similar pointing devices, as well as some cursor management tasks.
Please note that this ONLY discusses "mice" with the notion of the desktop GUI. You (usually) have one system cursor, and the OS hides the hardware details from you. If you plug in 10 mice, all ten move that one cursor. For many applications and games this is perfect, and this API has served hundreds of SDL programs well since its birth.
It's not the whole picture, though. If you want more lowlevel control, SDL offers a different API that gives you visibility into each input device, multi-touch interfaces, etc.
The other API is in SDL_input.h. See Input Device Support for more.
Those two APIs are incompatible, and you usually should not use both at the same time. But for legacy purposes, this API refers to a "mouse" when it actually means the system pointer and not a physical mouse.
