Re: [AD] GTK requirement

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


On Fri, 28 Dec 2012 17:42:34 +1100, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> On Wed, 26 Dec 2012 18:36:25 -0700, Trent Gamblin <nooskewl@xxxxxxxxxx> wrote:
> > 
> > I tried just using the Xlib drivers along with GTK at first but it
> > didn't work. It's either not possible or I'm too new to X programming
> > to figure it out.
> 
> I'll experiment with GtkSocket, maybe in the next few days.
> I previously added support for the XEmbed protocol, meaning an Allegro
> window can already be swallowed by a GtkSocket widget.  So we have the
> option of using GTK to create a window containing the GtkSocket, then
> swallowing the GLX window which we create ourselves, and which receives
> X input events as before.  We'd go via GTK to deal with the outer
> window, e.g. window resizing, setting the title bar, etc.

Done.  It seems to work fine.

> > I know that's not what you meant though. I agree,
> > it's not necessary to have input go through GTK for messageboxes. I
> > think the only thing that needs to be done is a gtk_init? So display
> > flags would work. We just would do an extra gtk_init, outside of the
> > gtk thread if ALLEGRO_GTK wasn't set.
> 
> Yeah, adding the flag would be easy.  gtk_init already exists in
> _al_gtk_ensure_thread, too.

Done.

I couldn't figure out how to make the top-level window expand
automatically when the menu is added, so that it doesn't eat into the
drawing area.  This happens with the Windows port as well.

I didn't look at implementing window size constraints at all.

Peter




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/