Re: [Flightgear-devel] Re: AirportList
--- Melchior FRANZ <[EMAIL PROTECTED]> wrote: > * Andrew Midosn -- Tuesday 25 January 2005 09:28: > > 59,60c58,60 > > < > > < true > > --- > > > > > > true > > > > > ... and make sure that you don't accidentally send > the patch to the > developer whose coding style you are "correcting" > along with your > functional changes, especially if these changes are > completely unrelated. > > m. :-] Ooops - I didn't notice that! I suspect it was the XML editor I was using deciding to enforce its own style. I certainly don't remember making any changes to that part of the file. I would normally try to adopt the coding style of the file I'm editing as far as possible - it's just polite. I'll go back to using vi I think - that's usually quite well behaved. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AirportList
* Andrew Midosn -- Tuesday 25 January 2005 09:28: > 59,60c58,60 > < > < true > --- > > > > true > > ... and make sure that you don't accidentally send the patch to the developer whose coding style you are "correcting" along with your functional changes, especially if these changes are completely unrelated. m. :-] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
--- Paul Surgeon <[EMAIL PROTECTED]> wrote: > On Monday, 24 January 2005 10:48, Erik Hofman wrote: > > Maybe it's even a better idea to have a world map > image where you can > > zoom in in three or four steps to select the > desired airport? > > If someone could add ssgContext support or some way > to render to a texture or > window inside of FG I could add it within 2 weeks. > I already have code that renders a textured WGS 84 > ellipsoid in OpenGL with > pan/zoom functionality. Adding airports to the globe > with picker support > would take no more than a day or two. > The only issue is that I'm using rather large > texture maps - it would take a > bit more work to add vector maps. > > This issue of not being able to render to a sub > window is coming back to bite > us everytime. If it's not stuff like this then it's > moving map/GPS/ND type > instruments. Now that sounds like the best idea overall. Mind you, assuming we had the ability to render to a sub-window, I think it's outside my abilities with C++ at present (Python might be a different matter). I'll keep tinkering away and learning for the moment, and wait impatiently for someone else to do the hard stuff! ;-) Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
On Monday, 24 January 2005 10:48, Erik Hofman wrote: > Maybe it's even a better idea to have a world map image where you can > zoom in in three or four steps to select the desired airport? If someone could add ssgContext support or some way to render to a texture or window inside of FG I could add it within 2 weeks. I already have code that renders a textured WGS 84 ellipsoid in OpenGL with pan/zoom functionality. Adding airports to the globe with picker support would take no more than a day or two. The only issue is that I'm using rather large texture maps - it would take a bit more work to add vector maps. This issue of not being able to render to a sub window is coming back to bite us everytime. If it's not stuff like this then it's moving map/GPS/ND type instruments. Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
Andrew Midosn wrote: I can understand Austin wanting to keep the airport file as lean as possible, but like yourself I think the country information is useful. I have only looked at a demo of X-Plane, but if I remember correctly the airport list is similar to FlightGear's - very long and hard to use. This is probably less of a problem for enthusiasts, who will tend to know the code for any airport they want to fly from, but is a pain for beginners who would be happier browsing a list. Maybe it's even a better idea to have a world map image where you can zoom in in three or four steps to select the desired airport? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
--- Paul Surgeon <[EMAIL PROTECTED]> wrote: > The country codes for airports are already Robin's > database - in fact he uses > them as part of the primary key. > > However he won't add it to the airport file because > X-plane doesn't use them > and Austin Meyer doesn't want anything in the > apt.dat that is not X-Plane > related. > > I feel that they should be added because they will > prove to be very valuable > for filtering but I haven't got enough weight to get > them added. I can understand Austin wanting to keep the airport file as lean as possible, but like yourself I think the country information is useful. I have only looked at a demo of X-Plane, but if I remember correctly the airport list is similar to FlightGear's - very long and hard to use. This is probably less of a problem for enthusiasts, who will tend to know the code for any airport they want to fly from, but is a pain for beginners who would be happier browsing a list. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
On Sunday, 23 January 2005 17:54, Andrew Midosn wrote: > It might be more useful to be able to apply a filter > to the list to reduce it in size. Probably filtering > by state for the USA and by country for (most) of the > rest of the world would be OK. Of course, we would > have to have access to that information, which I don't > think is available in apt.dat. I spoke to Robin Peel about this a couple of weeks ago. The country codes for airports are already Robin's database - in fact he uses them as part of the primary key. However he won't add it to the airport file because X-plane doesn't use them and Austin Meyer doesn't want anything in the apt.dat that is not X-Plane related. I feel that they should be added because they will prove to be very valuable for filtering but I haven't got enough weight to get them added. Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AirportList
* Andrew Midosn -- Sunday 23 January 2005 16:54: > --- Melchior FRANZ <[EMAIL PROTECTED]> wrote: > http://baron.flightgear.org/pipermail/flightgear-devel/2004-December/033009.html > > So it can't be done without changes to PLIB. Wrong conclusion. The current code depends on two plib functions being virtual, which they aren't. So the easiest fix was to make them virtual. But, of course, one can change the fgfs parts to work without that. > I'm thinking of anyone > that runs terrasync - they should have access to any > airport regardless of whether they currently have the > scenery available for it or not, shouldn't they? If terrasync would then download the respective terrain before fgfs puts you there, then yes. But this isn't the case, so it's pointless for now. You end up in sea either way. > It might be more useful to be able to apply a filter > to the list to reduce it in size. Probably filtering > by state for the USA and by country [...] Yes. > Of course, we would have to have access to that information, which > I don't think is available in apt.dat. Exactly. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
--- Melchior FRANZ <[EMAIL PROTECTED]> wrote: > http://baron.flightgear.org/pipermail/flightgear-devel/2004-December/033009.html So it can't be done without changes to PLIB. That's a shame. As far as scanning the scenery directory to work out which airports are available is concerned, I'm not sure that's the right solution. I'm thinking of anyone that runs terrasync - they should have access to any airport regardless of whether they currently have the scenery available for it or not, shouldn't they? It might be more useful to be able to apply a filter to the list to reduce it in size. Probably filtering by state for the USA and by country for (most) of the rest of the world would be OK. Of course, we would have to have access to that information, which I don't think is available in apt.dat. Just my opinion anyway. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AirportList
* Erik Hofman -- Sunday 23 January 2005 15:15: > Melchior FRANZ wrote: > > http://baron.flightgear.org/pipermail/flightgear-devel/2004-December/033009.html > > Melchior, as I understand this it requires a change in plib as well as > in FlightGear doesn't it (meaning there is no way to get it working > without the plib change)? > > If so, then the discussion must get a follow up in the plib developers > list (I assume it hasn't been discussed there already?) This patch was only thought to show what exactly fails and why. The patch was only a proof of concept. I didn't think it was acceptable to be applied. I had hoped that the author of this code part would comment on it, or that someone would give a hint for how to best fix it. Now 0.9.8 is out with this old bug (except some of the packagers modified his statically linked plib accordingly?). As the proper fix would be *not* to display 2 airports of which only 100 are installed, anyway, I'm not sure if the airport list deserves to survive, and if spending time for it is worth it. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AirportList
Melchior FRANZ wrote: http://baron.flightgear.org/pipermail/flightgear-devel/2004-December/033009.html Melchior, as I understand this it requires a change in plib as well as in FlightGear doesn't it (meaning there is no way to get it working without the plib change)? If so, then the discussion must get a follow up in the plib developers list (I assume it hasn't been discussed there already?) Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AirportList
* Andrew Midosn -- Sunday 23 January 2005 14:20: > The airport list control in the dialog is bound to the > airport-id property, and I had assumed that this would > be populated using the control's getStringValue() > method. But this method doesn't appear to get called > at all. http://baron.flightgear.org/pipermail/flightgear-devel/2004-December/033009.html m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
