Re: Designing objects with GObject

You can do this, as you control set_property().  The problem
is that this is a hack invisible to inspection, therefore it
can lead to all sorts of odd behaviour.

So it's exactly as I thought. I'll implement those properties separately for
both objects. I don't want to make any surprises to my code.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]