Melchior FRANZ wrote: > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:flightgear-devel- > [EMAIL PROTECTED] On Behalf Of > Sent: 14 April 2005 10:54 > To: flightgear-devel@flightgear.org > Subject: [Flightgear-devel] Re: CVS: FlightGear/src/GUI dialog.cxx, > 1.22,1.23 dialog.hxx, 1.7, 1.8 > > * Jim Wilson -- Wednesday 13 April 2005 22:32: > > In some cases you really need slightly more (but still brief) > information and > > not just a table of key bindings to get started. A scrolling text > window that > > always displays content from a particular property would do the trick. > > Done. It was easier than I had thought. So we currently have: > > <sim> > <help> > <title>Bo105</title> > <key> > <name>c/C</name> > <desc>select next/previous variant</desc> > </key> > > <line>This is a single line.</line> > <line>And this is another one.</line> > > <text>Multiline text > in scrollable > Field. > </text> > </help> > </sim> > > If no title is given, then /sim/description is used, and if that isn't > defined > either, then /sim/aircraft. Should the <text> field be called differently? > > > > > If there was any programming to be done, it'd be to extend the plib > puLargeInput > > widget in simgear with a text wrapping ability. > > Not done, because it's not needed yet. The respective aircraft maintainers > are > expected to keep their text column narrow enough. > > I've added those entries to almost all aircraft already. Of course, I'd > expect > the maintainers to remove/modify/extend as they like. There just should be > *something* for every aircraft. >
We, or rather the code, already know what the keys are. Any chance of generating this automatically, along the lines of the keys descriptions you already do? Otherwise, as you said, it will take years to cover all the aircraft. Regards, Vivian _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
