>>> Thanks Hernan. The problem is that I need a version that hasn’t been
built yet
Ok, Simon. Thanks.
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
test the new
CUSTOMQUITMESSAGE flag before release, please let me know.
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 15 July 2019 6:59 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
Hi folks,
We are going to release a new IUP version with t
Hi folks,
We are going to release a new IUP version with the changes I commited to
the SVN in the next couple of weeks.
Best,
Scuri
Em seg, 15 de jul de 2019 14:53, Hernan Cano
escreveu:
> Simon:
> The same site for IUP downloads has the DLLs you want.
> I can guide you if you want.
>
> By.
Simon:
The same site for IUP downloads has the DLLs you want.
I can guide you if you want.
By.
*HERNAN CANO MARTINEZ*
Analista de Sistemas
Cel: 300-782.48.44 (sólo llamadas)
WhatsApp: 316-601.12.67 (sólo WhatsApp)
El lun., 15 de jul. de 2019 a la(s) 12:35, Simon Orde escribió:
> Hi Scuri - th
July 2019 6:21 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
Hi,
I just committed to the SVN a new global attribute called CUSTOMQUITMESSAGE.
If set to Yes, the message processing it will use a custom quit message and it
will not call PostQuitMessage
uld behave as now and use PostQuitMessage.
>
>
>
> This would not only solve my problem, but also safely future-proof IUP
> over the issue going forward. What do you think?
>
>
>
> Simon
>
>
>
>
>
> *From:* Antonio Scuri [mailto:antonio.sc...@gmail
em, but also safely future-proof IUP over the
issue going forward. What do you think?
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 02 July 2019 1:15 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
Hi,
If you take a look
UP_DEFAULT;
>>
>> }
>>
>> }
>>
>>
>>
>>
>>
>> That’s it – except that there are a couple of comments in the same file
>> /* WM_QUIT */ that can simply be removed. The code in each case is fine as
>> it is and does not n
tness.
>
>
>
> Theoretically you could use WM_USER + ? as the message id, but it’s more
> robust to use a registered message. That way you can be 100% sure that
> there won’t be a conflict with any application-defined messages, which
> there could be if you took the WM_USER appr
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 24 June 2019 6:27 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
> Is there any way I can stop it doing that?
No
> Has IUP always posted WM_QUIT messages?
I think Yes
.
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 24 June 2019 6:27 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
> Is there any way I can stop it doing that?
No
> Has IUP always posted WM_QUIT messages?
I thi
ke one step in a long calculation
>
> -- update progress in some meaningful way
>
> gaugeProgress.value = i / 1
>
> -- allow the dialog to process any messages
>
> iup.LoopStep()
>
> -- notice the user wanting to cancel and do something meaningfu
celflag then break end
end
dlgProgress:destroy()
-- distinguish canceled from finished by inspecting the flag
print("cancled:",cancelflag)
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 20 June 2019 1:20 PM
To: IUP discussion list.
Subject: Re: [Iup-use
ms. What is it that they are doing which is different
> to what my script is doing?
>
>
>
> Simon
>
>
>
>
>
> *From:* Antonio Scuri [mailto:antonio.sc...@gmail.com]
> *Sent:* 19 June 2019 8:33 PM
> *To:* IUP discussion list.
> *Subject:* Re: [Iup-users] FW: I
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 19 June 2019 8:33 PM
To: IUP discussion list.
Subject: Re: [Iup-users] FW: IUP crash in Debug Mode
Ok.
Can you make a simple test? To replace IupButton by IupFlatButton and check
if there is any difference?
Be
Ok.
Can you make a simple test? To replace IupButton by IupFlatButton and
check if there is any difference?
Best,
Scuri
Em qua, 19 de jun de 2019 às 15:05, Simon Orde <
simono...@family-historian.co.uk> escreveu:
> … sorry – yet more clarification.
>
>
>
> When I said “if I modify the scri
… sorry – yet more clarification.
When I said “if I modify the script to add something (a message box) say, after
the call to “dlg:destroy()”, the message box code never gets called if I call
dlg:destroy.”
Again – what I meant is that if you click on the ‘OK’ button in the dialog, the
17 matches
Mail list logo