2.9.6 Widget support in Proxies

The Proxies provide a quite complex mechanism to handle updates in most of the widgets normally used in "forms". There is a reason for supporting these widgets: they are easily mapped to model attributes. This doesn't mean that you can't use other widgets in your Proxy interface, but there is no automatic update mechanism for it, and you will have to use your own handlers for them.

This is a reasonable property - it would be difficult to map what exactly the state of a gtk.Curve means to the model, for instance - and the Proxy can be extended in the future to support other widgets (write me if you are interested in contributing). What follows is a list of widget types supported, details on the use of them, and details about setting custom handlers if you need them.

The code in tests/test_Proxy.py offers a sample of using all the supported widgets in the same interface, and is highly recommended for study; it is however a bit too long to include in this text.



Footnotes

... grouping8
Alas, we can't use radiobutton's group() method to discover groups automatically because it is yet to be wrapped in PyGTK.
... catch9
A lively discussion could ensue about gtk.Combo and the lack of a signal that indicates an option was selected in its list, but I deliberately choose to avoid it!