Norman Vine wrote:
'Johnny' wrote:
Now, what broke?The 2D HUDYou still haven't answered what it is you want,The functionality of the 2D HUDSeriously, name your requirementSeriously, The functionality of the existing 2D HUDand we can try to meet it.
Thank you very much for the offer but since the requirement is nicely met by the existing code, there is nothing 'we' need to doNorman, I have the feeling this is getting to nowhere this way.
The 3D HUD code patch on the other hand needs to implement the "vestigial "if(1) {...}" in the patch" to make the HUD display
a 'properties' controlled option between the 2D and the 3D
versions or provide an alternative method of getting the existing
2D HUD displayed.
As it seems to me we (and by me I mean everybody using FlightGear, maybe except you) a 3D HUD. At this time we don't have one, and Andy created it. That's good.
Now we can do two things, have duplicate code by keeping the 2D HUD, or creating the functionallity of the 2D HUD with the nee 3D HUD code. I'm not for including two sets of code doing basically the same.
Please try to be a bit more coorporative in this, particularly because Andy _does_ want to satisfy *your* needs!
Erik
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
