mirror of
https://github.com/brl/mutter.git
synced 2024-11-27 02:20:43 -05:00
7c89a0ccfa
The :fullscreen property is very much confusing as it is implemented. It can be written to a value, but the whole process might fail. If we set: g_object_set (stage, "fullscreen", TRUE, NULL); and the fullscreen process fails or it is not implemented, the value will be reset to FALSE (if we're lucky) or left TRUE (most of the times). The writability is just a shorthand for invoking clutter_stage_fullscreen() or clutter_stage_unfullscreen() depending on a boolean value without using an if. The :fullscreen property also greatly confuses high level languages, since the same symbol is used: - for a method name (Clutter.Stage.fullscreen()) - for a property name (Clutter.Stage.fullscreen) - for a signal (Clutter.Stage::fullscreen) For these reasons, the :fullscreen should be renamed to :fullscreen-set and be read-only. Implementations of the Stage should only emit the StageState event to change from normal to fullscreen, and the Stage will automatically update the value of the property and emit a notify signal for it. |
||
---|---|---|
.. | ||
clutter-backend-x11-private.h | ||
clutter-backend-x11.c | ||
clutter-backend-x11.h | ||
clutter-event-x11.c | ||
clutter-stage-x11.c | ||
clutter-stage-x11.h | ||
clutter-x11-enum-types.c.in | ||
clutter-x11-enum-types.h.in | ||
clutter-x11-texture-pixmap.c | ||
clutter-x11-texture-pixmap.h | ||
clutter-x11.h | ||
clutter-x11.pc.in | ||
Makefile.am |