let's take the example of a button. the button may serve one or both of two purposes:
1) to provide a target for the user to operate on in order to change the state of some part of the "model" within the program (e.g. the state of some variable) - for example, by clicking/pressing itOn Thu, Apr 20, 2017 at 7:21 AM, Emmanuel Pacaud <emmanuel@xxxxxxxxx> wrote:
Hi Paul,
Le mer. 19 avril 2017 à 20:57, Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx> a écrit :
This normally means that you're not using appropriate model-view-controller design.
Could you elaborate a bit ? I fail to see where the design of my application could solve this issue I have with the use of Gtk.
Cheers,
Emmanuel.
On Wed, Apr 19, 2017 at 2:19 PM, Emmanuel Pacaud <emmanuel@xxxxxxxxx> wrote:
Hi,
Is there a way to unblock/block the emission of signals for a hierarchy of widgets ?
The reason I'm asking is because of this sort of code I'm using:
https://github.com/AravisProject/aravis/blob/master/viewer/ arvviewer.c#L588
It is not very convenient and error prone to register every connected signals and block/unblock them when one want to update some widgets programmatically.
Cheers,
Emmanuel.
_______________________________________________
gtk-list mailing list
gtk-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gtk-list
_______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list