🚀 go-pugleaf

In article <1992Aug3.203018.20678@m.cs.uiuc.edu>, zhou@m.cs.uiuc.edu (Tom Z.-Y. Zhou) writes:
|> I created a bunch of push buttons in my program using
|> WidgetKit::push_button(). But these button are way too long (or wide, if
|> you like) for my purpose. So my question is: can I customize the size of
|> a push button?

You should be able to use LayoutKit::fixed_span around a button
to override the default size.

|> Apparently WidgetKit, when called, creates an instance of one of its two
|> concrete sub-classes: MFKit and SMFKit. My guess is that SMFKit
|> is used in my case, since SMFKit::push_button_look()  sets the button width
|> to no less than 72. I wonder how SMFKit was chosen over the other. I
|> couldn't find any "define *motif_kit" in the InterViews source. And
|> adding "#define motif_kit; #undef sgi_motif_kit" in my code has no
|> effect. Weird. So the more general question is: can one have some degree
|> of control over WidgetKit, or is it simply a "Take it or leave it"
|> situation?

You can control the default kit via a resource (e.g., *gui:motif) or at build time
by changing KitFlags in iv/src/config/InterViews/local.def.