[310] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Stupid feature requests
daemon@ATHENA.MIT.EDU (Otto Hammersmith)
Thu Jun 12 12:53:14 1997
Date: Thu, 12 Jun 1997 12:52:03 -0400
From: Otto Hammersmith <otto@redhat.com>
To: gtk-list@redhat.com
In-Reply-To: <Pine.GSO.3.95q.970612112459.24101E-100000@augustus-239.cs.umn.edu>; from Shawn T Amundson on Thu, Jun 12, 1997 at 11:44:23AM -0500
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
On Thu, Jun 12, 1997 at 11:44:23AM -0500, Shawn T Amundson wrote:
> On Thu, 12 Jun 1997, Otto Hammersmith wrote:
>
> > On Thu, Jun 12, 1997 at 06:18:42PM +0300, Martynas Kunigelis wrote:
>
> > >
> > > 1. Why not make the button label/pixmap/whatever move along with the
> > > button itself when the button is clicked? Motif is the only toolkit
> > > that does not do this and why should gtk inherit bad things?
> >
> > Because it used to be that you could specify five different pixmaps
> > for the various states of a button. If you wanted a pixmap that
> > moved, you just provided another pixmap. It worked, but resulted in a
> > lot of excess code. (the advantage now is better handling of
> > backgrounds...)
> >
> > Apparently Spencer changed how GtkPixmap widgets work, so that may not
> > be the case any longer. I haven't had the time to look at it... so
> > I'm not sure there is a way to do it anymore. :-/
>
> Isn't this just a matter of shifting the widget that is in the button
> down and right 2(?) pixels? It shouldn't make a difference what widget it
> is, whether it's a label, pixmap, or a container with both.
Yeah, sorry... somehow I read label/pixmap/whatever as pixmap. I'm
not doing well today... *sigh*
So my question is, is it really -that- important? Seems like an awful
lot of work (not that it's hard) for something noone will hardly
notice.
--
-Otto.
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
