Am Freitag, 24. Juni 2011, 10:16:23 schrieb Carlos Barrales: > On Fri, Jun 24, 2011 at 9:44 AM, Sebastian Hilbert <
Hi all, Excellent news. wxgtk 2.8.11 really fixes the problem. While 2.8.11 is not available in Debian unstable it is available in Ubuntu 11.04 (Natty) I simply installed the Ubuntu package in Debian (which worked without errors) and it really did stop the crash in Ginkgo-CADx. I had to install libwxbase and libwxgtk2 from Ubuntu. Best regards, Sebastian > > [email protected]> wrote: > > Am Freitag, 24. Juni 2011, 09:14:27 schrieben Sie: > > > Hi. > > > > > > These are rather good news. > > > > > > We use 2.8.11 in our custom builds. > > > > > > Changing the string conversion methods in Ginkgo is a heavy task. I > > > will try to do it if I found some free time. (We are too busy right > > > now) > > > > I understand. So you are saying that you are more or less certain that > > the problem will go away when using wx 2.8.11 instead of 2.8.10 ? > > Can't fully confirm this unless it would be tested. > > > What about the string connversion methods ? Did they change between > > 2.8.10 and > > 2.8.11. > > Seems to be some due null character omitting. > http://trac.wxwidgets.org/changeset?old_path=%2FwxWidgets%2Ftrunk%2Fsrc%2Fc > ommon%2Fstrconv.cpp&old=56246&new_path=%2FwxWidgets%2Ftrunk%2Fsrc%2Fcommon% > 2Fstrconv.cpp&new=56394 > > > Or is it one of the patches in your custom build that makes the problem > > go away. > > Could be possible, but I am really convinced on it does not. At least in > this issue. > > > If you are certain that wx 2.8.11 will fix the crash then we have a > > stronger > > argument to ask for 2.8.11 or 2.8.12 in Debian. > > We think if we are right, that should be the best for all. > > Regards. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
