Hi,
I would recommend you to take a look at the IupLuaScripterDlg code in the
folder "iup\srclua5\scripter". It uses different colors for some fgcolor
styles.
IUP works very close with the Scintilla specs, so each IUP attribute is
almost a direct map to a Scintilla message. You can also
Thanks, that's from third party code. Except the LED parser, just removed
the unused function.
Best,
Scuri
Em ter, 4 de jun de 2019 às 16:22, Ranier VF
escreveu:
> Hi,
> Here some warnings coming from msvc compiler:
>
> c:\dll\iup\iup\srcmglplot\src\pde.cpp(221) : warning C4701: potentially
Hi,
Here some warnings coming from msvc compiler:
c:\dll\iup\iup\srcmglplot\src\pde.cpp(221) : warning C4701: potentially
uninitialized local variable 'ham' used
c:\dll\iup\iup\srcmglplot\src\prim.cpp(403) : warning C4701: potentially
uninitialized local variable 'n2' used
Hello,
I'm using IupScintilla today, and i'm having some issues with the
autocompletion.
I copied the example code to my cpp project, and it seems that the STYLEFGCOLOR
only works on the
10th style. So, operators have the right color, but everything else is black.
I tried to put the
Ok, but again the fix should be not there. That function should never be
called if value_len == 0.
Just added a second test in the calling function.
Em ter, 4 de jun de 2019 às 08:53, Ranier VF
escreveu:
> Hi,
> I would not be so sure.
> If value_len is exactly the size: 2
>
> if
Not exactly, the length is not at [0], it is actually before that. See:
https://docs.microsoft.com/en-us/previous-versions/windows/desktop/automat/string-manipulation-functions
So when we access BSTR pointers we can safely assume they are compatible
with WCHAR pointers. But when we create a
Hi,
BSTR are not WCHAR compatible.
See at:
https://www.codeguru.com/cpp/cpp/string/conversions/article.php/c5639/Guide-to-BSTR-and-C-String-Conversions.htm
"C strings are arrays of characters terminated by a NULL character. Visual
Basic strings differ in that the length of the string precede the
If you analyze the calling function that should never fail.
Em ter, 4 de jun de 2019 às 08:24, Ranier VF
escreveu:
> Hi,
> And what happens if "if (*value_max_size < value_len)" fail and
> realloc is not called?
>
> Best regards,
> Ranier Vilela
>
>
Hi,
And what happens if "if (*value_max_size < value_len)" fail and
realloc is not called?
Best regards,
Ranier Vilela
De: Antonio Scuri
Enviado: terça-feira, 4 de junho de 2019 11:09
Para: IUP discussion list.
Assunto: Re: [Iup-users] CID 210668 (#1 of
We use BSTR as the same definition of WCHAR, that's why we can do what we
do. In a more generic code that should work with BSTR variations then we
should be more careful. But that's not the case.
Best,
Scuri
Em seg, 3 de jun de 2019 às 23:05, Ranier VF
escreveu:
> Hi,
> Several fixes for
The realloc function does the malloc job. And it will only increase the
size of the value pointer when necessary.
Best,
Scuri
Em seg, 3 de jun de 2019 às 22:29, Ranier VF
escreveu:
> Hi,
> Sorry but can't undestand the logic.
> iupmatex_clipboard.c
> line 505, call function:
>
> value =
Thank you very much!
On Mon, Jun 3, 2019, 1:54 PM Antonio Scuri wrote:
> Just committed to the SVN:
>
>- *New: *XTICKFORMATNUMBER_CB and YTICKFORMATNUMBER_CB callbacks for
>*IupPlot*.
>
> They are called right before the tick number is drawn, so it can be used
> to change its
12 matches
Mail list logo
