Difference between revisions of "Types"

From uGFX Wiki
Jump to: navigation, search
(Basic)
Line 1: Line 1:
 
µGFX allows to write applications (eg. GUIs) that are completely portable as the library itself is highly agnostic. To achieve this goal, users should rely on the types exposed by µGFX as much as possible to prevent problems when migration to different systems.
 
µGFX allows to write applications (eg. GUIs) that are completely portable as the library itself is highly agnostic. To achieve this goal, users should rely on the types exposed by µGFX as much as possible to prevent problems when migration to different systems.
 +
 +
== Pre-Processor ==
 +
For pre-processing related boolean operations (eg. <code>#if MY_FEATURE</code>) use <code>GFXON</code> and <code>GFXOFF</code> accordingly.
  
 
== Basic ==
 
== Basic ==

Revision as of 15:49, 2 August 2021

µGFX allows to write applications (eg. GUIs) that are completely portable as the library itself is highly agnostic. To achieve this goal, users should rely on the types exposed by µGFX as much as possible to prevent problems when migration to different systems.

Pre-Processor

For pre-processing related boolean operations (eg. #if MY_FEATURE) use GFXON and GFXOFF accordingly.

Basic

Type Description
gBool A boolean value. Use gTrue and gFalse for assignments & comparisons respectively.
gI8 Signed integer at least 8 bits wide.
gU8 Unsigned integer at least 8 bits wide.
gI16 Signed integer at least 16 bits wide.
gU16 Unsigned integer at least 16 bits wide.
gI32 Signed integer at least 32 bits wide.
gU32 Unsigned integer at least 32 bits wide.

Rendering

Type Description
gCoord A type to express a coordinate in pixels.
gColor A color.
gFont A font. See font rendering.
gImage An image. See images.