> For example I'd strongly consider the missing options saving a bug that > has to be fixed before we give FlightGear to all the people out there. > They are used to this behavior from nearly every program they use, and > will expect the same from FG. Others may think, that we lived without > this feature (who doesn't have his own private preferences.xml in the > search path?) and it would be too an intrusive change. But that's the > difference between a developer and an end user release. > > Nine
I agree that this is a very serious feature for 1.0 inclusion. Maybe if we just have several people "signing off" the patch before inclusion (by 1) reading the code 2) testing it locally 3) sending an email to the list it's OK from their point of view for the 1.0) this will help. Personally, I will be willing to do this to the above patch. Vassilii _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
