gitea/SDL3_fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync SDL3 wiki -> header

Browse Source 
[ci skip]
This commit is contained in:
SDL Wiki Bot
2025-11-21 13:14:42 +00:00
parent 0f76744828
commit d9230f4796
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
include/SDL3/SDL_pen.h
View File

@@ -45,8 +45,8 @@
* connected. A pen leaving proximity (being taken far enough away from the * connected. A pen leaving proximity (being taken far enough away from the
* digitizer tablet that it no longer reponds) and then coming back should * digitizer tablet that it no longer reponds) and then coming back should
* fire proximity events, but the SDL_PenID should remain consistent. * fire proximity events, but the SDL_PenID should remain consistent.
* Unplugging the digitizer and reconnecting may cause future input to have * Unplugging the digitizer and reconnecting may cause future input to have a
* a new SDL_PenID, as SDL may not know that this is the same hardware. * new SDL_PenID, as SDL may not know that this is the same hardware.
* *
* Please note that various platforms vary wildly in how (and how well) they * Please note that various platforms vary wildly in how (and how well) they
* support pen input. If your pen supports some piece of functionality but SDL * support pen input. If your pen supports some piece of functionality but SDL
@@ -56,9 +56,9 @@
* how all USB mice connected to a computer will move the same system cursor. * how all USB mice connected to a computer will move the same system cursor.
* cursor. Other platforms might not support pen buttons, or the distance * cursor. Other platforms might not support pen buttons, or the distance
* axis, etc. Very few platforms can even report _what_ functionality the pen * axis, etc. Very few platforms can even report _what_ functionality the pen
* supports in the first place, so best practices is to either build UI to * supports in the first place, so best practices is to either build UI to let
* let the user configure their pens, or be prepared to handle new * the user configure their pens, or be prepared to handle new functionality
* functionality for a pen the first time an event is reported. * for a pen the first time an event is reported.
*/ */
#ifndef SDL_pen_h_ #ifndef SDL_pen_h_
@@ -81,12 +81,12 @@ extern "C" {
* *
* These show up in pen events when SDL sees input from them. They remain * These show up in pen events when SDL sees input from them. They remain
* consistent as long as SDL can recognize a tool to be the same pen; but if a * consistent as long as SDL can recognize a tool to be the same pen; but if a
* pen's digitizer table is physically detached from the computer, it might get * pen's digitizer table is physically detached from the computer, it might
* a new ID when reconnected, as SDL won't know it's the same device. * get a new ID when reconnected, as SDL won't know it's the same device.
* *
* These IDs are only stable within a single run of a program; the next time * These IDs are only stable within a single run of a program; the next time a
* a program is run, the pen's ID will likely be different, even if the * program is run, the pen's ID will likely be different, even if the hardware
* hardware hasn't been disconnected, etc. * hasn't been disconnected, etc.
* *
* \since This datatype is available since SDL 3.2.0. * \since This datatype is available since SDL 3.2.0.
*/ */