|
bWidgets
Core widget toolkit designed for Blender
|
Style-class for CSS driven Styles. More...
#include <bwStyleCSS.h>
Inheritance diagram for bWidgets::bwStyleCSS:
Collaboration diagram for bWidgets::bwStyleCSS:Public Member Functions | |
| bwStyleCSS () | |
| void | setWidgetStyle (bwWidget &widget) |
| void | polish (bwWidget &widget) |
Public Member Functions inherited from bWidgets::bwStyle | |
| virtual | ~bwStyle ()=default |
| virtual void | setWidgetStyle (bwWidget &widget)=0 |
| virtual void | polish (bwWidget &) |
Static Public Attributes | |
| static void(* | polish_cb )(bwWidget &widget) = nullptr |
Static Public Attributes inherited from bWidgets::bwStyle | |
| static unsigned int | s_default_widget_size_hint = 20 |
Additional Inherited Members | |
Public Types inherited from bWidgets::bwStyle | |
| enum class | TypeID { CLASSIC , CLASSIC_CSS , FLAT_GREY , FLAT_DARK , FLAT_LIGHT , BUILTIN_TOT } |
Public Attributes inherited from bWidgets::bwStyle | |
| TypeID | type_id |
| float | dpi_fac {1.0f} |
Protected Member Functions inherited from bWidgets::bwStyle | |
| bwStyle (TypeID type_id) | |
Style-class for CSS driven Styles.
How CSS is applied to styles may have to be reworked a bit. For now it just mattered to get something working (that is, making CSS control a style). Maybe every style should have the ability to be manipulated via CSS? We could for example store a CSS-Tree structure in each style that has priority over hardcoded style. It's also important to keep custom styles in mind. In the end, users should be able to 'install' a new style via a CSS file.
| bWidgets::bwStyleCSS::bwStyleCSS | ( | ) |
|
virtual |
Reimplemented from bWidgets::bwStyle.
|
virtual |
Implements bWidgets::bwStyle.
|
static |