Safe Haskell	None
Language	GHC2021

SDL3.Sys.Bindgen.Pen

Description

SDL pen event handling.

SDL provides an API for pressure-sensitive pen (stylus and/or eraser) handling, e.g., for input and drawing tablets or suitably equipped mobile / tablet devices.

To get started with pens, simply handle pen events:

SDL_EVENT_PEN_PROXIMITY_IN, SDL_EVENT_PEN_PROXIMITY_OUT (SDL_PenProximityEvent)
SDL_EVENT_PEN_DOWN, SDL_EVENT_PEN_UP (SDL_PenTouchEvent)
SDL_EVENT_PEN_MOTION (SDL_PenMotionEvent)
SDL_EVENT_PEN_BUTTON_DOWN, SDL_EVENT_PEN_BUTTON_UP (SDL_PenButtonEvent)
SDL_EVENT_PEN_AXIS (SDL_PenAxisEvent)

Pens may provide more than simple touch input; they might have other axes, such as pressure, tilt, rotation, etc.

When a pen starts providing input, SDL will assign it a unique SDL_PenID, which will remain for the life of the process, as long as the pen stays connected. A pen leaving proximity (being taken far enough away from the digitizer tablet that it no longer reponds) and then coming back should fire proximity events, but the SDL_PenID should remain consistent. Unplugging the digitizer and reconnecting may cause future input to have a 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 support pen input. If your pen supports some piece of functionality but SDL doesn't seem to, it might actually be the operating system's fault. For example, some platforms can manage multiple devices at the same time, but others will make any connected pens look like a single logical device, much how all USB mice connected to a computer will move the same system cursor. Other platforms might not support pen buttons, or the distance 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 let the user configure their pens, or be prepared to handle new functionality for a pen the first time an event is reported. SDL pen instance IDs.

Zero is used to signify an invalid/null device.

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 pen's digitizer table is physically detached from the computer, it might 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 a program is run, the pen's ID will likely be different, even if the hardware hasn't been disconnected, etc.

Since: 3.2.0

Synopsis

newtype SDL_PenID = SDL_PenID {
- unwrap :: Uint32
}
newtype SDL_PenInputFlags = SDL_PenInputFlags {
- unwrap :: Uint32
}
sDL_PEN_INPUT_DOWN :: CUInt
sDL_PEN_INPUT_BUTTON_1 :: CUInt
sDL_PEN_INPUT_BUTTON_2 :: CUInt
sDL_PEN_INPUT_BUTTON_3 :: CUInt
sDL_PEN_INPUT_BUTTON_4 :: CUInt
sDL_PEN_INPUT_BUTTON_5 :: CUInt
sDL_PEN_INPUT_ERASER_TIP :: CUInt
sDL_PEN_INPUT_IN_PROXIMITY :: CUInt
newtype SDL_PenAxis = SDL_PenAxis {
- unwrap :: CUInt
}
pattern SDL_PEN_AXIS_PRESSURE :: SDL_PenAxis
pattern SDL_PEN_AXIS_XTILT :: SDL_PenAxis
pattern SDL_PEN_AXIS_YTILT :: SDL_PenAxis
pattern SDL_PEN_AXIS_DISTANCE :: SDL_PenAxis
pattern SDL_PEN_AXIS_ROTATION :: SDL_PenAxis
pattern SDL_PEN_AXIS_SLIDER :: SDL_PenAxis
pattern SDL_PEN_AXIS_TANGENTIAL_PRESSURE :: SDL_PenAxis
pattern SDL_PEN_AXIS_COUNT :: SDL_PenAxis
newtype SDL_PenDeviceType = SDL_PenDeviceType {
- unwrap :: CInt
}
pattern SDL_PEN_DEVICE_TYPE_INVALID :: SDL_PenDeviceType
pattern SDL_PEN_DEVICE_TYPE_UNKNOWN :: SDL_PenDeviceType
pattern SDL_PEN_DEVICE_TYPE_DIRECT :: SDL_PenDeviceType
pattern SDL_PEN_DEVICE_TYPE_INDIRECT :: SDL_PenDeviceType

Documentation

newtype SDL_PenID Source #

C declaration: SDL_PenID, defined at SDL3/SDL_pen.h 93:16

Constructors

SDL_PenID
Fields unwrap :: Uint32

Instances

Instances details

Bits SDL_PenID Source #

Instance details