On 7/24/15, Antonio Scuri <antonio.sc...@gmail.com> wrote: > If all those modules I mentioned erlier are ready,
> iup*_common.c Mostly stubs. > iup*_dialog.c Create and destroy a window and set TITLE. > iup*_font.c Using the 2010 implementation of what actually compiles, the rest is stubbed out. > iup*_loop.c IupMainLoop/IupExitLoop implemented; enough to get typical programs running. > iup*_open.c Open and Close working. > iup*_key.c > iup*_focus.c > iup*_draw.c Just stubs here. I don't currently have much intuition about what I need these for or how I will verify/interact/see them. > then the next natural > steps are label and button. So I just started a label implementation. For a trivial test, I can see a label added to a dialog. (Ignoring things like positioning and fonts.) I still don't have a good understanding of how things get positioned and where I set these position values. (Note: Cocoa uses Cartesian coordinates like math books and OpenGL; y-axis increases going upwards.) For the official label test, it crashes when I try to add to a parent. In my debugger, the parent native handle is 0xffffffffffffffff. I'm expecting it to be the address of my window (the parent native widget). So I don't understand the system architecture well enough to understand why this value is 0xffffffffffffffff and what I'm supposed to be doing. ------------------------------------------------------------------------------ _______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
