On Thu, Jul 30, 2009 at 10:42:55AM +0200, Martin Nordholts wrote: > On 07/28/2009 12:40 PM, Roman Joost wrote: > > Hi, > > > > I wasn't sure if I should bring up this discussion on the mailing list > > or better on the bug report > > (http://bugzilla.gnome.org/show_bug.cgi?id=589474). > > [...] > > > > I'm working on another patch, which uses custom entry fields which > > "monitor" one property in the XMPModel. Currently they're subscribed to > > the 'row-changed' event in the XMPModel, which makes it hard to figure > > out if the change belongs to the Entry or not. If I could subscribe to a > > 'property-changed' event, I still have to figure out which property has > > changed, but don't have to figure out *if a property* has been changed. > > That would make life easier. > > Just to get a discussion going: Coulnd't you implement your own > "property-changed" and "schema-changed" in XMPModel? I.e. you would have > to write some wrappers on top of "row-changed" that provides nicer > callbacks than "row-changed". I could and the patch provided by that bug adds a custom 'property-changed' signal. Sven and Mitch thought, if I inherit from XMPModel, I wouldn't really need the 'property-changed' signal, because I'd be able to control the 'property-changed' signal. That is true, but maybe I wasn't clear enough saying, that I want to distinguish if a schema or a property changed by using different signals. Or I'm missing information ... Cheers, -- Roman Joost www: http://www.romanofski.de email: romanofski@xxxxxxxx
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
