many GObject implementations with construction properties need to execute some code after all CONSTRUCT and CONSTRUCT_ONLY properties have been set but before the object is regularly utilized by the g_object_new caller. the currently possible ways to implement such behavior are:

- count the CONSTRUCT properties that have been set already in set_property() and execute extra code if the last CONSTRUCT propety is set.

- override the special GObjectClass->constructor function pointer for every class that needs extra post-CONSTRUCT code and chain back to the original constructor of the class.

both ways are very cumbersome to implement and can hardly be recommended as good coding practice for object implementations. a much nicer way to hook up the required functionality would be the addition of a constructed() vmethod to GObjectClass which is called after the call to GObjectClass.constructor() is completed, but before g_object_new() returns.