[Flightgear-devel] Preclipped or overlapping layouts for apt.dat

2006-06-14 Thread bsupnik
Hi Y'all, One of the things that's come up in the apt.dat discussions is whether the taxiway layouts should be pre-clipped (meaning there are no overlapping polygons) or overlapped (meaning polygons can overlap and there is a well-defined draw order that makes one appear on top of another).

Re: [Flightgear-devel] Preclipped or overlapping layouts for apt.dat

2006-06-14 Thread Paul Surgeon
On Wednesday 14 June 2006 16:14, bsupnik wrote: - Pre-clipping puts more burdon on content creation tools (by requiring them to have robust clipping to save the data) whereas not requiring pre-clipping puts more work on data consumers. Where are you thinking of saving the clipped data? Back

Re: [Flightgear-devel] Preclipped or overlapping layouts for apt.dat

2006-06-14 Thread bsupnik
Hi Paul, For what it's worth, I'm leaning more and more toward overlapping, both because of your arguments, stuff Curt's said, and just tossing the ideas around...so this is a bit of a devil's advocate argument... Paul Surgeon wrote: Where are you thinking of saving the clipped data? Back

Re: [Flightgear-devel] Preclipped or overlapping layouts for apt.dat

2006-06-14 Thread Arnt Karlsen
On Wed, 14 Jun 2006 10:14:18 -0400, bsupnik wrote in message [EMAIL PROTECTED]: Hi Y'all, One of the things that's come up in the apt.dat discussions is whether the taxiway layouts should be pre-clipped (meaning there are no overlapping polygons) or overlapped (meaning polygons can