X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Cam-AntiVirus:	no malware found
X-Cam-SpamDetails:	not scanned
X-Cam-ScannerInfo:	http://www.cam.ac.uk/cs/email/scanner/
Resent-Date:	Tue, 20 Sep 2011 10:02:33 +0100
Resent-Message-Id:	<E1R5wDp-00004q-YT AT ppsw-51 DOT csi DOT cam DOT ac DOT uk>
From:	Peter Clifton <pcjc2 AT cam DOT ac DOT uk>
To:	gEDA user mailing list <geda-user AT moria DOT seul DOT org>
Cc:	geda-user AT seul DOT org
In-Reply-To:	<201109182306.p8IN6Urr024218@envy.delorie.com>
References:	<j5325n$k8m$1 AT dough DOT gmane DOT org>
	<201109181645 DOT p8IGjlBj009564 AT envy DOT delorie DOT com>
	<j55bpp$4q8$1 AT dough DOT gmane DOT org>
	<201109182306 DOT p8IN6Urr024218 AT envy DOT delorie DOT com>
Mime-Version:	1.0
Subject:	Re: gEDA-user: windows and opengl
Resent-From:	Peter Clifton <pcjc2 AT cam DOT ac DOT uk>
Resent-To:	geda-user AT delorie DOT com
Date:	Tue, 20 Sep 2011 10:02:13 +0100
X-Mailer:	Evolution 3.1.91-
Message-ID:	<1316509353.11746.0.camel@localhost>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--=-a0jsQ1AKaio8/woQG59v
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, 2011-09-18 at 19:06 -0400, DJ Delorie wrote:
> > Is there a serious road block?=20
>=20
> Yes - the code just doesn't work.  The PCB window is very messed up,
> including no menus or sidebar and a misaligned crosshair.

What environment are you testing under for that?

For me, it works (with the GTK patches), the only misalignment or visual
glitch I see is where the crosshair is immediately underneath the mouse
pointer "icon".

Aside from the minor problem under the cursor, I do see a crash when
certain polygons are drawn. That is a show-stopper for now. The crash
isn't present on my pcb+gl_experimental branch, so I'm assuming it is
related to the GLU tesselator code tripping over some "bad" input.

The same input on Linux doesn't cause any issue, but it will be using
mesa's GLU code, not (wherever the GLU code from windows comes from).

> > Can I tell potential users that this will most likely be rectified
> > on a reasonable time frame -- Say in, in a few months?
>=20
> Officially, no - it's our policy to not make such predictions, but if
> you want to fix it yourself in the next few months, you may promise
> them that.  Otherwise, we'll work on it if/when we get a chance and it
> will get fixed when it's fixed.

I could provide a build of one of my branches which (hopefully) doesn't
contain the crash. I'll need to select a suitable commit though, as the
layer opacity changes I've got in those branches are obviously not right
yet.

This would be an unofficial release, and will likely be less maintained
with regard to bugs than the official PCB one. (I just don't have a good
development setup for Windows).

Best wishes,

--=20
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

--=-a0jsQ1AKaio8/woQG59v
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAABAgAGBQJOdwq3AAoJEOo4D/b1x+QV2g8H/jLxrEWgmXYrbb5c2ztiK7Ty
VeANpi6+CjTEEtG1z6ZZ2pNUJjKZzzsiNlFjFWM9ug51oyBjpNQg3n+hW2R9tmfj
F2R/qNmkzHM1OYDcHeuAzDhrQL0TE/EJ8kVZ0ADJTAMG3UUJI4vmdELuuArn3ewa
VMNrNuUrH6dqDuoFAEue5ZDkfAk63jpow1pkReXpuvddVYXf6cEYGXVksi09Uv76
st3N3qCcZTFb5uJJa2eCj+Cr5DmVKzO9YL4Ces0evVc52gdsTw6DhFpt3N2kLKFC
7bsa8NL8yyjGzjFwxNDDf3AtaIYOLj1ZjqvbBdi5Z+WsM/D5lneMGXK1cDezq88=
=uDAO
-----END PGP SIGNATURE-----

--=-a0jsQ1AKaio8/woQG59v--

- Raw text -