Re: Gtk.Image.Gtk_Image

[Thomas <fantome.forums.tDeContes@free.fr.invalid>]

In article <t1pb0r$elh$1@gioia.aioe.org>,
 "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote:

> On 2022-03-26 18:32, Thomas wrote:

> > should i prefer to call Gtk.Image.Show as soon as possible, when
> > creating mcc.tki.Image.External_Image?
> > or should i call Gtk.Image.Show only at the time it is really displayed,
> > when creating mcc.tki.Widget.Picture.Picture?
> 
> I usually create new widgets derived from a container, more or less 
> always. GtkAda allows this nicely. Then in my implementation of 
> Initialize for the custom I call Show at its end. I never had issues 
> with this approach.

it doesn't help me. no matter. I made a choice :-)



> > it asks the user to choose the position and size of each widget, instead
> > of ask him to make stacks with automatic layout management, like Gtk
> > does with Gtk_Box.
> 
> Yes, using GTK in a totally non-GTK way.

:-)

> I had this problem designing my 
> GTK/Cairo-based library for instruments like meters, gauges etc. I used 
> relative positions and sizes instead of fixed ones to support resizing 
> the top-level dashboard widgets. Plus hacks for keeping or not keeping 
> aspect ratio of the resized thing. The base is Gtk_Drawing_Area_Record 
> rather than Gtk_Fixed_Record.

i don't think it's pertinent to apply full flexibility to all widgets, 
but :

as is, i get 2 differents behaviors :

- with Tcl/Tk, the window can be fully resized, the overflowing widgets 
are hidden, and still shown when the window is enlarged.

- with GTK, the window cannot be fully resized, it is forbidden to hide 
any widget set in the Gtk_Fixed.


any opinion ?

-- 
RAPID maintainer
http://savannah.nongnu.org/projects/rapid/