On Mon, 2005-10-03 at 19:57 +0200, Melchior FRANZ wrote: > * Melchior FRANZ -- Monday 03 October 2005 19:47: > > * Durk Talsma -- Monday 03 October 2005 18:08: > > > > (B) which bugs need to be fixed (and by whom :-)? > > > > > - Setting a wrong path for --fg-scenery results in an abort > > > > I'll look into this. > > It behaves exactly as it is supposed to: If no paths are given, > the default is used. If paths are given, fgfs uses all that do > actually contain scenery. (It doesn't complain about paths that > don't!) But if a user specifies one or more paths but *none* > contains valid scenery, it aborts with this error message: > > Fatal error: No valid scenery path defined! > > What do you think fgfs should do with no scenery? I consider > this bug "fixed". :-) >
"Works for me" might be closer. If flightgear can't find valid scenery in the area specified, what else can we do about it? Perhaps, popping up a dialog box but the message is okay. George _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
