9 Mar
2014
9 Mar
'14
8:06 p.m.
Hey Devs,
I was reviewing some of the ponyscape merge today and I noticed in the object's dialog Janeczko used signal.block() and signal.unblock() to deny signals and I suspect to prevent loops and such.
Is this a good pattern to use?
I've come across several places where looks are caused by update and refresh signals locking up. Everything from image.cpp's update to filters dialog reorder signal. And what I found interesting was how sp-use deals with this problem. It puts update signals on a glib callback and has a mass of code for preventing the problems that sp-image.cpp gets into a lot.
I'd love to hear from those more experienced with C++, GLib and signals about the best pattern to use.
Best Regards, Martin Owens