Hi
IupFileDlg is a full native dialog. We don't have much control over it.
DEFAULTENTER and DEFAULTESC works only on regular IupDialogs.
Best,
Scuri
Em sex., 8 de jan. de 2021 às 11:48, Pete Lomax via Iup-users <
iup-users@lists.sourceforge.net> escreveu:
> When the IupFileDlg opens,
Hi,
You have to download the pdflib source package available with the CD
download files.
Best,
Scuri
Em qui., 7 de jan. de 2021 às 19:52, navegantes carlinhos <
navegan...@yahoo.com.br> escreveu:
> Feliz ano ano para todos ! Happy new year 2021
>
> I am building the module accoding to
On 08/01/2021 13:57, Antonio Scuri wrote:
> Hi Scott,
> local dlg = iup.GetDialog(self)
Ah! Thank you, that's exactly the thing I was looking for.
Scott
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
When the IupFileDlg opens, it expands to the specified directory but then
appears to perform an ensure_visible(node0) operation, making "C:" top line and
said target directory off-screen (but still somehow with focus).
Clearly the keyboard handling of Alt-M for Make new folder, DEFAULTENTER and
Hi Scott,
In the callbacks of the two buttons I would store a value, for instance
"status", on the dialog.
function ok_but:action()
local dlg = iup.GetDialog(self)
dlg.status = true
end
function cancel_but:action()
local dlg = iup.GetDialog(self)
dlg.status = false
end
So after
On 08/01/2021 12:11, Johann Philippe via Iup-users wrote:
> Hey ,
> I use lsignal : https://github.com/cpp11nullptr/lsignal
>
> It is a Qt like signal/slot system. You can call a signal from both
> click actions in iup, with a different value.
Sorry, should have been clearer. I'm working on Lua
Hey ,
I use lsignal : https://github.com/cpp11nullptr/lsignal
It is a Qt like signal/slot system. You can call a signal from both click
actions in iup, with a different value. Let's say something like :
// declare signal
lsignal::signal clickSig;
// call it from click actions
Assume you have some iup.dialog with Cancel and OK buttons, where their
action events return iup.CLOSE.
What's the best way to find which button the user closed the dialog with
from an dlg:popup call?
I can think of a few methods, but they all seem clunky (i.e. setting a
global)
Scott
