X11workbench Toolkit
1.0
|
Data Structures | |
struct | WBFont |
An allocated structure containing XFontStruct, XFontInfo, and XftFont [as applicable] for a specified font. More... | |
struct | WBFontInfo |
Internal structure, caching font information (mostly for legacy font support) More... | |
Typedefs | |
typedef struct WBFont * | WB_FONT |
An allocated structure containing XFontStruct, XFontInfo, and XftFont [as applicable] for a specified font. More... | |
typedef const struct WBFont * | WB_FONTC |
a 'const' version of WB_FONT - note that this CAN actually be written to, so it's not truly 'const'. More... | |
typedef struct WBFontInfo | WB_FONT_INFO |
Internal structure, caching font information (mostly for legacy font support) More... | |
X11 Workbench Toolkit font-related structures
An allocated structure containing XFontStruct, XFontInfo, and XftFont [as applicable] for a specified font.
Internal structure, caching font information (mostly for legacy font support)
a 'const' version of WB_FONT - note that this CAN actually be written to, so it's not truly 'const'.
In order to implement font objects that are not modified, that is the actual system font they represent does not change, the 'WB_FONTC' type is used. This helps to prevent accidentally modifying the font objects returned as 'WB_FONTC'. In the 'C' language there's no obvious way to implement a 'const' that isn't exactly 'const', when you store the cached query information (and forward/back chain pointers) directly into it 'on the fly'. So don't use read-only memory to store a WB_FONTC . The details will be taken care of on the back-end. This also causes the C compiler to perform some implicit type conversions so that the code works.
Definition at line 185 of file font_helper.h.