Top |
These functions provide stylesheets and icons for the interfaces. Unless
you have passed -DGNUISANCE_BUILD_FLAG_MANUAL_ENVIRONMENT
while compiling
the library, you do not need to to invoke them manually.
If you are not using libgnuisance in its entirety (-lgnuisance
), but are
using only some of its modules (-lgnuiflow
, -lgnuitaggedentry
, etc.),
the names of these functions will have different prefixes equal to those
of the modules that you are using. For example, if you are only using the
tagged entry library (-lgnuitaggedentry
),
will be named gnuisance_environment_init()
. You will also not
have it advertised in any public header, and so you will have to addgnui_tagged_entry_environment_init()
1 |
extern void gnui_tagged_entry_environment_init (void); |
to your compilation unit. The stylesheets and icons loaded by these
per-module functions are only those required by the specific modules. Some
modules, like -lgnuiflow
, do not provide any ..._environment_...()
function.
When compiling the library, widgets that do provide their
..._environment_...()
functions can be prevented individually from
autoloading stylesheets and icons by passing
-DGNUI..._BUILD_FLAG_MANUAL_ENVIRONMENT
per-module directives
(e.g. -DGNUI_EMBLEM_PICKER_BUILD_FLAG_MANUAL_ENVIRONMENT
,
-DGNUI_TAGGED_ENTRY_BUILD_FLAG_MANUAL_ENVIRONMENT
, etc.).
void
gnuisance_environment_init (void
);
Load the library's GResource
objects
Each invocation after the first one will silently be no-op.
gboolean
gnuisance_environment_get_is_initialized
(void
);
Get if the library's GResource
objects are loaded or not