Re: [gtkmm] pack_start and AttachOptions is still confusing
- From: Murray Cumming <murrayc usa net>
- To: Michael Babcock <mbabcock la creatureshop henson com>
- Cc: gtkmm-list <gtkmm-list gnome org>
- Subject: Re: [gtkmm] pack_start and AttachOptions is still confusing
- Date: 18 Jul 2002 22:20:38 +0100
On Thu, 2002-07-18 at 22:08, Michael Babcock wrote:
> Murray Cumming wrote:
> I've attached a patch against gtkmm-1.3.18 to implement this. I'm new to
> gtkmm internals, gtkmmproc, and doxygen, so please fix it as needed.
Patches should go in bugzilla and should patch the ChangeLog. See
www.gtkmm.org/bugs.shtml for further instructions.
> Because Gtk::AttachOptions is still used in Gtk::Table and Gtk::Paned, I
> created a new enumeration, Gtk::PackOptions. Because SHRINK would
> conflict with the existing AttachOptions SHRINK, I renamed it CONTRACT.
> "Contract" is a synonym for "shrink" and an antonym for "expand"
> according to the thesaurus at m-w.com.
>
> This is the new enumeration:
> /** Packing options for adding child widgets to a Box with pack_start()
> and pack_end(). */
> enum PackOptions {
> CONTRACT, /**< Space is contracted to the child widget size. */
> EXPAND_PADDING, /**< Space is expanded with extra space filled with
> padding. */
> EXPAND_WIDGET /**< Space is expanded with extra space filled by
> increasing the child widget size. */
> };
[snip]
> Now for Gtk::Table, I'm not sure what to do. We seem to have deduced
> that in this case an independent Gtk::FILL does serve a purpose, but the
> interface is certainly not easy to figure out. I haven't looked at
> Gtk::Paned at all.
So maybe we should have PACK_SHRINK, PACK_EXPAND_PADDING, and
PACK_EXPAND_WIDGET, and separate ATTACH_* enum values.
--
Murray Cumming
murrayc usa net
www.murrayc.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]