On Sun, 5 Aug 2007 10:10:22 +0200 Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> * Syd&Sandy -- Sunday 05 August 2007: > > Ive added ascii properties to the autopilot route-manager waypoints , > > the same as the Instrumentation/nav id , because adding 2d text to the > > Primus 1000 PFD and MFD makes it difficult to > > re-use in other aircraft , and the 2d text is harder to read and scale > > properly .... > > Sorry, I don't understand that. "because adding 2d text [...] is > difficult to re-use". Huh?? Letters are no harder to re-use than > their ASCII numbers. And foo[0] in Nasal gives you the ASCII number. > So why do we want the number in the property tree? Can you give an > example? > > > > > If that is OK with everyone , could someone commit it please ? > > You don't need to copy the string to a character array to access > the letters as ASCII numbers. This works just as well: > > string foo = "ABCD"; ... int(foo[0]) ... > > I don't agree with the underscores. Almost all properties use > hyphens, and we should keep it at that. It's more consistent and > thus easier to remember. I can live with underscores in properties > like "level-gal_us", where this stands for a space between name > and unit, but I'm routinely converting other properties from > underscore to hyphens. Please don't *add* more of them. > > And finally: property names shouldn't contain digits. Those should > internally be converted to indices, but you shouldn't rely on that. > And id_asc1 is a bad property name. The abbreviation doesn't buy > us anything. That's a tiny bit less typing replaced by guessing > every time someone looks at it. Why not id-ascii[1]? > > m. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi m. Its simply a copy of a routine in navradio.cxx , which contains all of the no no's you described above... By difficult to re use I mean by overlaying a 2d panel on the PFD screen , it involves a fair bit of work to resize and orient the instrument area properly , and I'm trying to make it a bit more "modular". I would prefer the textranslate method , so I need a "position" for each character in the string... I didn't realize the same thing could be done in Nasal , if so , so much the better... I'll look into your string foo = "ABCD"; ... int(foo[0]) ... suggestion... Cheers -- Syd&Sandy <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
