G'day,
Subject says a lot:
1. Looking forward to the new release. Thank you so much for all the effort.
2. I've tracked your Ubuntu/GNU/Linux build documentation, and adding
"libfftw3-dev" is sufficient to pull all requirements in. IM now builds
successfully.
[On a "purist" level, I
> Yes, that could be very interesting. I'm closing a new version now. We could
> plan it for the next version.
Great, how can I help?
regards,
Ranier Vilela
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists
>I have some basic code in C that creates a couple of elements and tries to
>print out the list of attributes associated >with one of them (a text area in
>the example below), but when I run it, all the attribute names I expected to
>see are >NULL even though IupGetAllAttributes said there would
Hi,
There is a small error here:
IupOpen(&argc, &argv);
But it is not related with the IupGetAllAttributes behavior.
This:
int names_count = IupGetAllAttributes(text, NULL, -1);
Returns the maximum number of that call may return. Those 7 are all
internal attributes, so the next
Hi,
Yes, that could be very interesting. I'm closing a new version now. We
could plan it for the next version.
Best,
Scuri
Em qui., 30 de jul. de 2020 às 16:28, Ranier Vilela
escreveu:
> Hi Scuri,
>
> I would like suggest a new feature to IUPList:
> Actually normal behavior (Windows) is
Hi,
I'm running your Lua test code here, using the main.cpp program. I
pressed 5 times the Done button, it worked ok. The dialog is closed every
time. The I run again and closed the dialog in the system close button X.
It closed ok too. I alternate between Done and Close, ok too. I uncomment
t
I have some basic code in C that creates a couple of elements and tries to
print out the list of attributes associated with one of them (a text area in
the example below), but when I run it, all the attribute names I expected to
see are NULL even though IupGetAllAttributes said there would be se
Hi Scuri,
I would like suggest a new feature to IUPList:
Actually normal behavior (Windows) is find a ITEM by first letter only.
Extended behavior when user type a text.
Find a ITEM by users type text (invisible buffer)
Windows can use CB_FINDSTRING message
GTK (?)
Motif (?)
Example:
Windows nor
