Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Antonio Scuri
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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Ranier Vilela
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]-&

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Antonio Scuri
, 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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Ranier Vilela
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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Antonio Scuri
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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Ranier Vilela
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.

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Antonio Scuri
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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Ranier Vilela
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

Re: [Iup-users] IUP assorted issues (part IV)

2020-07-16 Thread Antonio Scuri
> 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

[Iup-users] IUP assorted issues (part IV)

2020-07-12 Thread Ranier Vilela
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