[Glade-users] Userdefined Widgets in catalog file

[tristan.van.berkom at gmail.com (Tristan Van Berkom)]

On Thu, Apr 27, 2017 at 12:17 AM, Elmar Haneke <elmar at haneke.de> wrote:
> > So, to explain a bit better, in order to augment a widget's properties
> > with completely made up properties, it's mostly important to just
> > specify the type of property it is, take for example the "size"
> > property of the GtkBox (which does not get saved to the Glade file,
> > but that does not have to be the case).
>
> Ok, that does solve the main problem, glade seems to silently ignore
> incomplete property information.
>
> Can you give me some hints about defining signals?

Sorry Elmar,

This is something that was just never implemented. To be honest the
fact that you can do virtual properties like this is partly
accidental, the primary use case for this was to introduce virtual
properties in the property editor that would not be saved, but simply
allow plugin editor authors to provide a more convenient user
experience for editing widgets.

That said, over the years this has come up a couple of times and it
would be nice to be able to declare entirely virtual signals for your
type of use case, where the widget you want to edit is not going to be
available in a regular C library.

Cheers,
    -Tristan