Re: Gtk.Image.Gtk_Image

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2022-03-26 18:32, Thomas wrote:
> In article <t1mkkt$1vs3$1@gioia.aioe.org>,
>   "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote:
> 
> since it can be made before call to Gtk.Container.Add, that raises a new
> question:
> 
> 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.

>> So it tries to manage the layout
>> by itself instead of using the prescribed techniques. Then Gtk_Fixed is
>> a way to go.
> 
> 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.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de