Ok.
Em qua, 19 de jun de 2019 às 15:03, Simon Orde <
simono...@family-historian.co.uk> escreveu:
> To be precise, when I said “If I run the iup dialog script from my
> previous post… in (Visual C++) debug mode … it will close the application”,
> I meant: “… it will close the application *if*
cation die so
> suddenly like that. So there’s no useful information to be gleaned from
> the call stack. It’s usually sitting just below the main message loop at
> this point.
>
>
>
> Does any of that suggest anything?
>
>
>
> Simon
>
>
>
>
>
>
To be precise, when I said “If I run the iup dialog script from my previous
post… in (Visual C++) debug mode … it will close the application”, I meant: “…
it will close the application if you click on the OK button in the dialog”. It
will not close the application if you click on the ‘X’ in the
gleaned from the call stack. It’s usually sitting
just below the main message loop at this point.
Does any of that suggest anything?
Simon
From: Antonio Scuri [mailto:antonio.sc...@gmail.com]
Sent: 19 June 2019 11:52 AM
To: IUP discussion list.
Subject: Re: [Iup-users] IUP
Hi Simon,
I can't see anything wrong with your script.
First, what do you mean by Debug Mode? Are you debugging the Visual C++
application or the Lua script? When not in debug mode it works?
Second, you have a very peculiar configuration as we speak previously.
Maybe you will have to bui
Hi - I'm using Lua 5.3 and IUP 3.26 to run embedded Lua scripts in my Visual
C++ 2017 application, and I'm having problems with IUP dialogs which cause
my application to crash - but only in debug mode. For example, the
following script will cause my application to crash if (and only if) you
click
