[Iup-users] Layout/sizing bug with GTK3 backend

Hi, I want to report that I’ve found some kind of bug in the IUP GTK3 backend concerning layout/sizing. The bug seems to have gotten a lot worse recently. Before: I was using an older build of IUP, maybe 6 months to a year old. With the layout I was doing in my program, text labels seem to be siz

Re: [Iup-users] IUP trunk=iup_dlglist.c (dereferencing a potential null pointer)

I will try to build in a fresh installation and let you guys know. Yes, I'm in a rush for next week. But I still have 1 final task. Best, Scuri Em seg, 4 de nov de 2019 15:31, Simon Orde escreveu: > Hi Ranier > > I am also looking for an IUP build that works with MSVC 2017. In my case I

Re: [Iup-users] IUP trunk=iup_dlglist.c (dereferencing a potential null pointer)

Hi, "I am also looking for an IUP build that works with MSVC 2017. In my case I really need a 32-bit build (although I'm also interested in a 64-bit build). If you work out how to build under MSBC 2017 (64 bit, or 32, but ideally both), please let me know how you did it. I spent some time on this

Re: [Iup-users] IUP trunk=iup_dlglist.c (dereferencing a potential null pointer)

Hi Ranier I am also looking for an IUP build that works with MSVC 2017. In my case I really need a 32-bit build (although I'm also interested in a 64-bit build). If you work out how to build under MSBC 2017 (64 bit, or 32, but ideally both), please let me know how you did it. I spent some time o

Re: [Iup-users] IUP trunk=iup_attrib.c (dererencing a potential null pointer)

That can never happen. If it does then nothing will work in IUP. One of the most sensible parts in IUP is its hash table. And it proved so far it is quite reliable. Best, Scuri Em seg., 4 de nov. de 2019 às 13:57, Ranier VF escreveu: > Hi, > Dererencing a potential null pointer at line 294.

Re: [Iup-users] IUP trunk=iup_dlglist.c (dereferencing a potential null pointer)

That won't be ok. Because there maybe dialogs ready to be destroyed after i>idlg_count. The code is protected by the iupObjectCheck call. It may read from an invalid memory, but it will correctly check the pointer. Best, Scuri Em seg., 4 de nov. de 2019 às 14:08, Ranier VF escreveu: > Hi,

[Iup-users] IUP trunk=iup_dlglist.c (dereferencing a potential null pointer)

Hi, Dereferencing a potential null pointer (ih_array), lines 122, 116. --- \dll\iup\a\src\iup_dlglist.cThu Jul 25 16:27:06 2019 +++ iup_dlglist.c Mon Nov 04 13:47:53 2019 @@ -115,7 +115,7 @@ int i = 0, count; Ihandle** ih_array = (Ihandle**)malloc(idlg_count * sizeof(Ihandle*)

[Iup-users] IUP trunk=iup_attrib.c (dererencing a potential null pointer)

Hi, Dererencing a potential null pointer at line 294. --- \dll\iup\a\src\iup_attrib.c Thu Oct 03 21:48:51 2019 +++ iup_attrib.cMon Nov 04 13:51:57 2019 @@ -287,12 +287,12 @@ /* store the names before updating so we can add or remove attributes during the update */ name = iupTableF

Re: [Iup-users] IUP Compilation with msvc 2017

Hi Scuri, " From a past experience, it is not the iup_array.c that is not being found. It a visual c++ dependency. That's why I suggested the shortcut also." Thanks solved with Ming64, your right. Thank you. Ranier Vilela De: Antonio Scuri Enviado: segu

Re: [Iup-users] IUP Compilation with msvc 2017

Hi Scuri, With --trace enabled E:\dll\iup\iup>win-make --trace makefile:9: target 'iup' does not exist win-make --no-print-directory -C ./src/ iup makefile:12: target 'iup' does not exist win-make --no-print-directory -f ../tecmakewin.mak TEC_UNAME=dll15 ../tecmakewin.mak:244: target 'print-start'

Re: [Iup-users] IUP Compilation with msvc 2017

Hi, From a past experience, it is not the iup_array.c that is not being found. It a visual c++ dependency. That's why I suggested the shortcut also. One good test is to to copy that command line, and manually run it in a regular prompt. Best, Scuri Em seg, 4 de nov de 2019 12:28, Ranier

Re: [Iup-users] IUP Compilation with msvc 2017

Hi Scuri, "Or the shortcut "Developer Command Prompt for VS 2017"." Yes this, this is being done. But the compilation still stop at iup_array.c Thanks. Ranier Vilela De: Antonio Scuri Enviado: segunda-feira, 4 de novembro de 2019 15:09 Para: IUP discussio

Re: [Iup-users] IUP Compilation with msvc 2017

Hi, The folders are not being created because the GNU mkdir must be installed. The cmd internal mkdir will not work. For now, our build system is based on GNU, so we need GNU compatible tools. We are considering moving to CMake in a near future. But now you will need to download MSYS too. S

Re: [Iup-users] IUP Compilation with msvc 2017

Hi, Some progress, after creating manually all obj and lib. E:\dll\iup\iup>win-make --debug GNU Make 4.1 Built for i686-w64-mingw32 Copyright (C) 1988-2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are f

Re: [Iup-users] IUP Compilation with msvc 2017

Hi, trying with debug enabled. E:\dll\iup\iup>make --debug GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for

[Iup-users] IUP Compilation with msvc 2017

Hi Scuri, Windows 64 bits msvc 2017 set TEC_UNAME=dll15 set VC15=c:/progra~2/micros~2/2017/community/vc set NO_DEPEND=Yes ''; echo 'Tecmake: Starting [ iup:dll15 ]' if [ ! -d ../obj/dll15 ] ; then mkdir -p ../obj/dll15 ; fi ! foi inesperado neste momento. ../tecmakewin.mak:1662: recipe for target