Re: [Dclib-devel] Menus

[Davis K. <dav...@us...>]

On Fri, Apr 4, 2008 at 12:44 PM, Nils Labugt <el...@on...> wrote:

>
>
> An almost complete rewrite. I only recognize the two drawing functions
> and the PNG loader.


Yeah, it sort of turned out that way.  Initially I thought it would be
easier but as I was writing the abstract files it was simpler to just
rewrite a lot of parts than understand and merge everything.  I also don't
want to have any pointers in the code so that necessitated a bunch of
changes too.  There is a lot to be said for having a working prototype while
doing it though :)



>
> >  so it is hard to keep track of the differences or parts I might be
> > missing.    But the things that are in there now are a menu_bar,
> > popup_menu, 3 popup_menu_item styles (a text style, a submenu style,
> > and a horizontal line style), the dlib::button now takes a style
> > argument as well but I only have two styles in there, and there is
> > also a tooltip widget.
>
> I haven't compiled anything yet, I have only looked at the code. I don't
> see any icon button? And what about the user_action classes? They would
> make it easier to separate GUI code from the rest of the program.


I just added a button_style_toolbar_icon1 style into subversion.   There are
certainly a lot more to add though.

I had a hard time understanding exactly what the user_actions were doing
from looking at the code.  I get the general idea I think but it isn't
obvious to me how they are better than just having
member_function_pointers?


>
> > you know how to get unicode key codes out of X11 and win32 events?
>
> I have attached some code I found in xterm. It is a script that
> generates a C file (keysym2ucs.c) that converts keysyms to Unicode. The
> file header of the generated file says it is in the public domain. (I'm
> not sure about the comments, they seem to be derived from
> UnicodeData.txt.) I think there is a different way to obtain Unicode
> input in newer versions of X11. (Languages like Chinese require more
> complicated methods for keyboard input.)
>

Ok, I'll look at all of this stuff.