Date: Wed, 17 Feb 2010 10:56:12 +0100 From: Horst Leitenmueller <horst.leitenmueller@liwest.at> To: Jonathan Chen <jonathan.chen@solnetsolutions.co.nz> Cc: sepotvin@FreeBSD.org, freebsd-java@freebsd.org Subject: Re: java/clipse port Message-ID: <1266400572.84221.18.camel@lap01> In-Reply-To: <28080_1266347041_4B7AEC1B_28080_109_1_4B7AEC1D.3000101@solnetsolutions.co.nz> References: <19598_1266267945_4B79B728_19598_10_1_4B79B72B.2080809@solnetsolutions.co.nz> <1266310527.92266.68.camel@lap01> <28080_1266347041_4B7AEC1B_28080_109_1_4B7AEC1D.3000101@solnetsolutions.co.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, it's not depending on the port or version of eclipse, as i read its a problem of the gtk team that they have changed something which has a deep impact on the eclipse implementation.... at the moment i think there is a no changing situation on both sides...but who knows... what would be nice, would be an information on the eclipse port itself when installed to handle the problem, or an integration into /usr/local/eclipse/eclipse to start with the flag on (like ubuntu did) perhaps the portmaintainer could check a solution ?! A) Info or B) patch for the executable to set the Flag directly br horst On Wed, 2010-02-17 at 08:03 +1300, Jonathan Chen wrote: > On 16/02/2010 21:55, Horst Leitenmueller wrote: > > hi is it only on updating ? > > > > perhaps its this bug with gtk+> 2.18 > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=291257 > > > > open a terminal > > setenv GDK_NATIVE_WINDOWS true > > > > or > > export GDK_NATIVE_WINDOWS=true > > Thanks for that! It does appear to a Eclipse+GTK related bug. > At least there's a workaround, and it allows me to continue working. > > I wonder if there's any chance of a more recent port of Eclipse in > the works? Perhaps 3.5.x (Galileo)? > > Cheers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1266400572.84221.18.camel>