[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk-devel
Subject:    Re: #50218 -  Notification on write-only properties is questionable/problematic
From:       Bill Haneman <Bill.Haneman () Sun ! COM>
Date:       2001-03-28 17:33:32
[Download RAW message or body]


>To: Bill Haneman <Bill.Haneman@Sun.COM>
>Cc: timj@gtk.org, gtk-devel-list@gnome.org
>Subject: Re: #50218 -  Notification on write-only properties is 
questionable/problematic
>From: Owen Taylor <otaylor@redhat.com>
>Date: 28 Mar 2001 12:27:37 -0500
>User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
>
>
>Bill Haneman <Bill.Haneman@Sun.COM> writes:

...
>> I'm a little worried about preventing this notification...

...

>The point here is: what would you do when you got
>notification of a change to a writeonly property?  You can't
>retrieve the new value...

Yep, it would only be useful if we knew the internals
well enough to predict the knock-on effects, and
queried them.

>The only writeonly property I know of in GTK+ at the
>moment is GtkLabel::pattern, which is an alternate
>method of setting the ::attributes property, which
>is read-write.

...
>When you set the ::pattern attribute, you get notification
>that ::attributes has changed.
>
>I expect that most write-only attributes will be like
>this - an alternate way of setting a readwrite property.7

Yes, for ::pattern it is a non-issue.  I hope that's 
generally the case!


-Bill

>Regards,
>                                        Owen

------
Bill Haneman x19279
Gnome Accessibility / Batik SVG Toolkit
Sun Microsystems Ireland 


_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

[prev in list] [next in list] [prev in thread] [next in thread]