* Syd&Sandy -- Sunday 05 August 2007:
> On Sun, 5 Aug 2007 11:30:09 +0200 Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> > ... but only with wanting to use the ascii code as offset in an
> > alphabet stripe on a texture. In that case (and if Nasal can't be
> > used) we should think about a different way to achieve that. It can't
> > be that for every text on instruments we also have to push a series
> > of ASCII values into the property tree. That's bad design.
> I could be wrong , but I personally think a render to texture would be
> the best route ,
Possibly. Can't judge that. Mathias' or Tim's business. :-)
One could just add a parameter to the animations where it's needed (or
better to a generic "input channel" class used by all animations) that
defines that not n.getDoubleValue() should be used to read the value,
but int(n.getStringValue()[pos]), where pos is read from <string-position>:
<animation>
<type>textranslate</type>
<property>/whatever/waypoint/id</property>
<string-position>0</string-position>
<offset>-48</offset>
...
</animation>
or something. :-)
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
