Just a warning. I observed that forking a process while iup is running
is prone to error. So I forked one child early on to process async
stuff and use nanomsg to talk to it. Further forks are handled by that
child. Much safer to use.
Am 14.07.2015 um 17:38 schrieb Antonio Scuri:
> It could
It could be something related with your fork, because in C, execution
returns after calling IupPopup always.
Best,
Scuri
Em 14/07/2015 12:20, "Eric Wing" escreveu:
> On 7/14/15, Antonio Scuri wrote:
> > That's the normal behavior of IupPopup. It blocks execution until the
> > modal dialog is
On 7/14/15, Antonio Scuri wrote:
> That's the normal behavior of IupPopup. It blocks execution until the
> modal dialog is closed. The progress dialog is a regular IupDialog so, yes,
> it can be used with IupShow and IupPopup.
>
> Best,
> Scuri
>
Hmmm, I don't think that's what I'm seeing. So in
That's the normal behavior of IupPopup. It blocks execution until the
modal dialog is closed. The progress dialog is a regular IupDialog so, yes,
it can be used with IupShow and IupPopup.
Best,
Scuri
On Tue, Jul 14, 2015 at 11:40 AM, Eric Wing wrote:
> I want my progress dialog to be modal, s
I want my progress dialog to be modal, so I would like to use IupPopup
with it. The documentation doesn't make any mention of this (just
Show).
I tried using it and noticed that all statements that come after
IupPopup in my function don't get executed. I moved this call to the
end of my function.
