Allow checking initialization without side-effects
authorEmmanuele Bassi <ebassi@linux.intel.com>
Fri, 19 Jun 2009 13:09:42 +0000 (14:09 +0100)
committerEmmanuele Bassi <ebassi@linux.intel.com>
Fri, 19 Jun 2009 13:09:42 +0000 (14:09 +0100)
commitb5f4befeaa2d1944c7623a31f8a8ccaae200b640
treee8b98ffea2fa45500645a996c74b0c5eeab884c9
parent184df2a5fa34375cff8cde5318ba46bdbd7c3026
Allow checking initialization without side-effects

The _clutter_context_get_default() function will automatically
create the main Clutter context; if we just want to check whether
Clutter has been initialized this will complicate matters, by
requiring a call to g_type_init() inside the client code.

Instead, we should simply provide an internal API that checks
whether the main Clutter context exists and if it has been
initialized, without any side effect.
clutter/clutter-main.c
clutter/clutter-private.h