20,741
edits
No edit summary |
|||
Line 21: | Line 21: | ||
{{cquote| | {{cquote| | ||
Yes, reset and save/restore are a bit broken in FlightGear right now. I'll try to fix them when I have a chance, but it will require a bit of refactoring (removing Curt's initial-state stuff, for example).<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18869.html |title= Re: Helicopters: wow!|author=David Megginson |date=Mon, 24 Nov 2003 07:22:13 -0800}}</ref>|David Megginson}} For details, see [[Fixing Presets]]. | Yes, reset and save/restore are a bit broken in FlightGear right now. I'll try to fix them when I have a chance, but it will require a bit of refactoring (removing Curt's initial-state stuff, for example).<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18869.html |title= Re: Helicopters: wow!|author=David Megginson |date=Mon, 24 Nov 2003 07:22:13 -0800}}</ref>|David Megginson}} For details, see [[Fixing Presets]]. | ||
{{cquote| | |||
The original reset was a simple kludge that worked fine for a simple program; now that FlightGear is a lot more sophisticated, we need to refactor a bit | |||
rather than just holding things together with scotch tape and bubble gum. | |||
The problem is that right now we have two different approaches - a lot of stuff is handled cleanly in individual modules' update() methods, but a lot of stuff is still handled by hundreds of lines of BASIC-like, hard-to-read spaghetti code in main.cxx and fg_init.cxx (forget OO, it's not even functional programming). | |||
That was the right idea to get started - I'm not a fan of wasting time on an initial OO design that you won't end up using -- but now we need to finish cleaning it up. We need to make this a high priority.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg06781.html|title= Crash on "Reset" function.|author=David Megginson |date=Thu, 06 Jun 2002 05:03:39 -0700}}</ref>|David Megginson}} | |||
== Solution == | == Solution == |