Yes, it will always return non NULL in that context.
Best,
Scuri
Em qua, 15 de jan de 2020 18:14, Ranier Vilela
escreveu:
> Hi Scuri,
>
> I did not understand your answer, for me still with error.
> Do you mean that IupGetCallback (tree, "SELECTION_CB");
> always return different than NULL
Hi Scuri,
I did not understand your answer, for me still with error.
Do you mean that IupGetCallback (tree, "SELECTION_CB");
always return different than NULL in that context?
regards,
Ranier Vilela
De: Antonio Scuri
Enviado: quarta-feira, 15 de janeiro
Hi,
It is true, but not in that context. There SELECTION_CB must be defined.
Best,
Scuri
Em qua., 15 de jan. de 2020 às 09:39, Ranier Vilela
escreveu:
> Hi,
>
> IupGetCallback function can return NULL, therefore it is necessary to
> check the return.
>
> best regards,
> Ranier
Hi,
the bug was actually here:
if (fprintf(file, "function load_image_%s()\n", name) < 0)
fprintf should not be called, replaced by iImagePrint
Thanks for reporting.
Best,
Scuri
Em qua., 15 de jan. de 2020 às 09:43, Ranier Vilela
escreveu:
> Hi,
>
> The var file is not properly
Hi,
Thanks, but this is an internal callback used only for memory monitoring.
It is actually supposed to be called after the handle has been released.
Added a few comments.
Best,
Scuri
Em qua., 15 de jan. de 2020 às 08:47, Ranier Vilela
escreveu:
> Hi,
> win\iupwin_image.c (line 887)
>
>
Hi,
Maybe your clean all left something behind.
I just rebuild the dll10 and it linked ok.
Best,
Scuri
Em qua., 15 de jan. de 2020 às 08:09, Ranier Vilela
escreveu:
> Hi,
> After clean all. The msvc claims this:
>
> ll10/iupwin_val.obj ../obj/dll10/iupwin_touch.obj
>
Hi,
The var file is not properly protected, when call fprintf, and can be NULL.
"passing null pointer file to fprintf" message from static tool analyser.
best regards,
Ranier Vilela
iup_export.patch
Description: iup_export.patch
___
Iup-users mailing
Hi,
IupGetCallback function can return NULL, therefore it is necessary to check the
return.
best regards,
Ranier Vilela
iup_layoutdlg.patch
Description: iup_layoutdlg.patch
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
Hi,
win\iupwin_image.c (line 887)
handle is freed at line 872, and is passed to function cb if has
IMAGEDESTROY_CB.
function cb they have no way of knowing that the pointer is invalid!
Wouldn't it be better to call cb first, and then release the pointer?
regards,
Ranier Vilela
Hi,
After clean all. The msvc claims this:
ll10/iupwin_val.obj ../obj/dll10/iupwin_touch.obj ../obj/dll10/iupwin_tabs.obj .
./obj/dll10/iupwin_menu.obj ../obj/dll10/iupwin_list.obj ../obj/dll10/iupwin_tre
e.obj ../obj/dll10/iupwin_calendar.obj ../obj/dll10/iupwin_datepick.obj ../obj/d
Hi Scuri,
I am compiling iup trunk with msvc 2010, and are reporting the error below,
could you help?
ll10/draw.obj ../obj/dll10/fill.obj ../obj/dll10/font.obj ../obj/dll10/image.obj
../obj/dll10/init.obj ../obj/dll10/memstream.obj ../obj/dll10/misc.obj ../obj/d
ll10/path.obj
11 matches
Mail list logo