[prev in list] [next in list] [prev in thread] [next in thread]
List: gtk-devel
Subject: Re: gtk_widget_set/get_flags() (Re: GTK_FLOATING broken in 2.9?)
From: Matthias Clasen <matthias.clasen () gmail ! com>
Date: 2005-12-14 13:13:05
Message-ID: cbccc63c0512140513m71fe16bbk8159c8528997e076 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
On 12/14/05, Tim Janik <timj@imendio.com> wrote:
>
> On Tue, 13 Dec 2005, Matthias Clasen wrote:
>
> > On 12/13/05, Murray Cumming <murrayc@murrayc.com> wrote:
> >>
> >>
> >>>
> >>> gtkmm 2.8 depends on glib/gtk 2.8, right? then you don't have
> >>> g_object_force_floating() there. would it be of any help to you
> >>> if glib 2.8 had g_object_force_floating() already (whether function
> >>> or not)?
> >>
> >> Yes, or something in GTK+. Though it would be an act of desparation.
> >
> >
> > One could conceivably modify GTK_OBJECT_SET_FLAGS to do the right thing
> for
> > floating, but
> > direct setting/checking of the flag is not fixable.
>
> hmmmmm.
>
> my take on this is that the only way to go this route would be along the
> lines of introducing:
>
> void gtk_widget_set_flags (GtkWidget *widget, guint64 flags);
> guint64 gtk_widget_get_flags (GtkWidget *widget);
> /* this is reflected by ::notify::flags */
>
> and *deprecating* GTK_OBJECT_SET_FLAGS(), GTK_OBJECT_GET_FLAGS(),
> GTK_WIDGET_SET_FLAGS() and GTK_WIDGET_GET_FLAGS() while changing their
> implementations to use gtk_widget_*et_flags().
>
> for most flags, modification through GTK_OBJECT_SET_FLAGS() already is
> wrong
> and you should use proeprties instead.
Coincidentally, we have an old bug about deprecating GTK_WIDGET_SET_FLAGS()
and
replacing them all by properties...bug *69872.*
Matthias
[Attachment #5 (text/html)]
<br><br><div><span class="gmail_quote">On 12/14/05, <b class="gmail_sendername">Tim \
Janik</b> <<a href="mailto:timj@imendio.com">timj@imendio.com</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tue, 13 Dec 2005, \
Matthias Clasen wrote:<br><br>> On 12/13/05, Murray Cumming <<a \
href="mailto:murrayc@murrayc.com">murrayc@murrayc.com</a>> \
wrote:<br>>><br>>><br>>>><br>>>> gtkmm 2.8 depends on \
glib/gtk 2.8, right? then you don't have<br>>>> g_object_force_floating() \
there. would it be of any help to you<br>>>> if glib 2.8 had \
g_object_force_floating() already (whether function<br> >>> or \
not)?<br>>><br>>> Yes, or something in GTK+. Though it would be an act of \
desparation.<br>><br>><br>> One could conceivably modify \
GTK_OBJECT_SET_FLAGS to do the right thing for<br>> floating, but <br>> direct \
setting/checking of the flag is not fixable.<br><br>hmmmmm.<br><br>my take on this is \
that the only way to go this route would be along the<br>lines of \
introducing:<br><br>void gtk_widget_set_flags (GtkWidget \
*widget, guint64 flags); <br>guint64 gtk_widget_get_flags (GtkWidget *widget);<br>/* \
this is reflected by ::notify::flags */<br><br>and *deprecating* \
GTK_OBJECT_SET_FLAGS(), GTK_OBJECT_GET_FLAGS(),<br>GTK_WIDGET_SET_FLAGS() and \
GTK_WIDGET_GET_FLAGS() while changing their <br>implementations to use \
gtk_widget_*et_flags().<br><br>for most flags, modification through \
GTK_OBJECT_SET_FLAGS() already is wrong<br>and you should use proeprties \
instead.</blockquote><div><br><br>Coincidentally, we have an old bug about \
deprecating GTK_WIDGET_SET_FLAGS() and <br>replacing them all by properties...bug \
<b>69872.</b><br><br>Matthias<br></div><br></div><br>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic