1) About the main loop. I think it is quite similar to the GTK:
int IupMainLoop(void)
{
gtk_main();
return IUP_NOERROR;
}
That's ok.
2) UnMap will be called only when you destroy the dialog. IUP does not
automatically destroy its dialogs.
Best,
Scuri
On Thu, Jul 23, 2015 at 6:01 PM, Eric Wing <ewmail...@gmail.com> wrote:
> On 7/23/15, Antonio Scuri <sc...@tecgraf.puc-rio.br> wrote:
> > Hi,
> >
> > In the iup/test folder there are several small applications that covers
> > many aspects of every control. The dialog.c test does not depends on any
> > other control.You can show just the dialog without any control inside.
> This
> > is essential to test specific diaog features.
> >
> > Very interesting the GNUstep framework. I can be very useful. Thanks
> for
> > pointing that out.
> >
> > Best,
> > Scuri
> >
> >
>
>
> I just pushed some initial changes to get a window on screen.
>
> My first question is about the event loop. In Cocoa, Apple really
> wants to take over the event loop. Basically, you call [NSApp run] (or
> their even higher level functions like NSApplicationMain() and the
> system takes over.) While it is possible to manually pump the event
> loop and not call [NSApp run], in my experience, there are a lot of
> edge cases where things don't work quite right. For example, I've seen
> bugs with menu focus and more complicated Apple APIs that seem to
> depend on private magic inside Apple's private implementation of run.
>
> Currently, if I don't use run and manually pump, the keyboard shortcut
> Cmd-Q and menu action for Quit don't work. I'm not sure how to fix
> that yet. But I'm wondering if Iup's architecture would allow me to
> just call run. That would mean I need to use Cocoa event callbacks for
> every interesting event and manipulate/notify Iup through those
> callbacks.
>
>
> Second, I'm now putting up a simple window through the dialog API.
> I've also hooked up a Cocoa callback when the user hits the close
> button which allows me to accept the close or reject it. I'm looking
> at the GTK iupgtkDialogDeleteEvent as what I think should happen in
> this callback. However, I noticed that the actual window memory is not
> deallocated here and instead happens in an UnMap callback. I'm not
> sure how to trigger the UnMap callback. It never goes off for me.
>
> Thanks,
> Eric
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Iup-users mailing list
> Iup-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iup-users
>
>
------------------------------------------------------------------------------
_______________________________________________
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
