| Re: [AD] Menus and Callbacks |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Mon, 2004-11-08 at 18:13 -0800, Chris wrote:
> On Mon, 08 Nov 2004 13:11:34 +0100, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> > Not in the core lib I'd say. But we'll have to think what to do about
> > things like grabber or file_select_ex.
>
> The old API will, hopefully, still be there.. but I don't know if
> we're going to be making a new API for the GUI. We could just leave it
> as-is in the compatibility directory.
>
Yep. As long as we need it in the compatibility layer anyway, can as
well use if for graber.
> In all honesty, I kind of like Allegro's GUI. The only problem is that
Me too. Except some small things on it, like the mentioned active_menu
global. Another problem with the menus is, in gui_menu_draw_menu_item,
you can't find out the parent menu (which makes proper theming
impossible). I wonder if a menu->proc_ex and a
gui_menu_draw_menu_item_ex would make sense.
> it takes direct access to the screen (it doesn't allow for easy use of
> double buffering or page flipping) and the default widget look is very
Hm, yes - could simply have a gui_screen, or a function
show_gui(target_bitmap). (Completely synchronous access, splitting
update_dialog into process_dialog and render_dialog, probably wouldn't
work.)
> bland. We could actually change how the default procedures look,
> though.. AFAIK there's nothing stating what they look like.. as long
> as they behave right.
>
Could use one of the basic AGUP themes.
--
Elias Pschernig