22:36
> Para: IUP discussion list.
> Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>
> > This is the output here:
>
> >cpoints[0]->x=180
> >cpoints[0]->y=50
> >cpoints[1]->x=180
> >cpoints[1]->y=20
> >cpoints[2]->x=230
> &g
De: Antonio Scuri
Enviado: quinta-feira, 16 de julho de 2020 22:36
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues (part IV)
> This is the output here:
>cpoints[0]->x=180
>cpoints[0]->y=50
>cpoints[1]->x=180
>cpoints[1]->y=20
>cpoints[2]-&
,
Scuri
Em qui., 16 de jul. de 2020 às 17:55, Ranier Vilela
escreveu:
> De: Antonio Scuri
> Enviado: quinta-feira, 16 de julho de 2020 19:00
> Para: IUP discussion list.
> Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>
> > Yes, there are two integers there. And
De: Antonio Scuri
Enviado: quinta-feira, 16 de julho de 2020 19:00
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues (part IV)
> Yes, there are two integers there. And we provide an array with twice the
> size, but count still contains just the >number of poin
020 18:50
> Para: IUP discussion list.
> Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>
> >> Why Coverity claims this?
> >> 4. access_dbuff_in_call: Calling Polygon indexes array (POINT *)points
> with index count.
> >> Polygon expect param const
De: Antonio Scuri
Enviado: quinta-feira, 16 de julho de 2020 18:50
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>> Why Coverity claims this?
>> 4. access_dbuff_in_call: Calling Polygon indexes array (POINT *)points with
>> index count.
reveu:
> De: Antonio Scuri
> Enviado: quinta-feira, 16 de julho de 2020 18:33
> Para: IUP discussion list.
> Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>
> >> 1. Memory corruption at src/iup_draw.c
> >> variable points has size of 6, but call Polygon with
De: Antonio Scuri
Enviado: quinta-feira, 16 de julho de 2020 18:33
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues (part IV)
>> 1. Memory corruption at src/iup_draw.c
>> variable points has size of 6, but call Polygon with only size 3.
>> iupdrvDra
> 1. Memory corruption at src/iup_draw.c
> variable points has size of 6, but call Polygon with only size 3.
> iupdrvDrawPolygon call msvc Polygon function
Count is the number of points, not the size of the array.
> 2. Memory corruption at srcglcontrols/iup_gldraw.c
> variable points has size
Hi Scuri,
Here some new issues with IUP.
1. Memory corruption at src/iup_draw.c
variable points has size of 6, but call Polygon with only size 3.
iupdrvDrawPolygon call msvc Polygon function
2. Memory corruption at srcglcontrols/iup_gldraw.c
variable points has size of 6, but call Polygon with o
*1. Possible dereference null at functions iFlatTreeTextEditVALUECHANGED_CB
andiFlatTreeTextEditKCR_CB (src/iup_flatree.c)Function iFlatTreeGetNode can
return NULL, so, var nodefocus can be NULL*
That can never happen in the context of that function.
*2. Uninitialized var used (src/win/iupw
Hi Scuri,
There are some news issues with IUP-3.29
1. Possible dereference null at functions iFlatTreeTextEditVALUECHANGED_CB and
iFlatTreeTextEditKCR_CB (src/iup_flatree.c)
Function iFlatTreeGetNode can return NULL, so, var nodefocus can be NULL
2. Uninitialized var used (src/win/iupwin_clipbo
De: Antonio Scuri
Enviado: terça-feira, 7 de julho de 2020 18:05
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues (part II)
> All changes committed to the SVN.
Thank you.
regards,
Ranier Vilela
___
Iup-users mailing list
*1. src/iup_elempropdlg.c& operator is dangerous, need parentheses to
clarify expression.*
OK
*2. iup_flatscrollbar.c!show_transparent test is always true, can be secure
removed.*
OK
*3. src/iup_gauge.cNot sure, IupDrawEnd(ih); is missing call?*
Yes, it was missing. Thanks.
*4. src/i
7. src\win\iupwin_fontdlg.c (195)
height_pixels = logfont.lfHeight; <- reassigned value?
8. src\win\iupwin_key.c (105)
map[VK_OEM_PLUS].iupcode = LOWORD(MapVirtualKeyA(VK_OEM_PLUS,
MAPVK_VK_TO_CHAR));
map[VK_OEM_COMMA].iupcode = LOWORD(MapVirtualKeyA(VK_OEM_COMMA,
MAPVK_VK_TO_CHAR));
map[V
Hi Scuri,
More issues with latest trunk.
1. src/iup_elempropdlg.c
& operator is dangerous, need paranteses to clarify expression.
2. iup_flatscrollbar.c
!show_transparent test is always true, can be secure removed.
3. src/iup_gauge.c
Not sure, IupDrawEnd(ih); is missing call?
4. src/iup_image.
Do you want me to reply to this because I would gladly reply to it.
Em qua., 3 de jun. de 2020 às 21:36, Ranier Vilela
escreveu:
De: Andrew Robinson
Enviado: quarta-feira, 3 de junho de 2020 23:23
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues
>so I'm ignoring
De: Antonio Scuri
Enviado: quarta-feira, 1 de julho de 2020 22:22
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues
> Just commited to the SVN. Thanks for the report and fixes.
You are welcome.
regards,
Ranier Vilela
___
avoid it, but I don't know if it's the expected
behavior. *
The rename was enough.
Just commited to the SVN. Thanks for the report and fixes.
Best,
Scuri
Em qua., 3 de jun. de 2020 às 21:36, Ranier Vilela
escreveu:
> De: Andrew Robin
De: Andrew Robinson
Enviado: quarta-feira, 3 de junho de 2020 23:23
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues
>so I'm ignoring you from now on.
Please, do me this favor.
___
Iup-users mailing list
I
r like yours,
so I'm ignoring you from now on.
Regards,
Andres
On 2020-06-03 at 3:14 PM, Ranier Vilela wrote:
>De: Antonio Scuri
>Enviado: segunda-feira, 1 de junho de 2020 16:50
>Para: IUP discussion list.
>Assunto: Re: [Iup-users] IUP assorted issues
>
> > Ok. I&#x
Assunto: Re: [Iup-users] IUP assorted issues
>
> > Ok. I'll take a look. Thanks.
> Scuri, can we move to for whatever matters that really matter to IUP,
> Did you get a look at the patch?
>
> regards,
> Ranier Vilela
>
>
De: Antonio Scuri
Enviado: segunda-feira, 1 de junho de 2020 16:50
Para: IUP discussion list.
Assunto: Re: [Iup-users] IUP assorted issues
> Ok. I'll take a look. Thanks.
Scuri, can we move to for whatever matters that really matter to IUP,
Did you get a look at the patch?
regards
Ok. I'll take a look. Thanks.
Best,
Scuri
Em sex., 29 de mai. de 2020 às 19:54, Ranier Vilela
escreveu:
> Hi Scuri,
>
> Attached, new patch, with numerous suggestions for various corrections.
> Please review the patch, any questions, I am available.
> I will try to summarize some of the prob
Hi Scuri,
Attached, new patch, with numerous suggestions for various corrections.
Please review the patch, any questions, I am available.
I will try to summarize some of the problems encountered, but as there are
many, it may be that some of them have passed.
1. \ src \ iup_colorbrowser.c (184)
25 matches
Mail list logo
