On mardi 11 novembre 2008, Melchior FRANZ wrote:
> * gerard robin -- Saturday 08 November 2008:
> > Is it so difficult, to include within FG, the code which
> > gives the information, or at least, to include as generic
> > the 'famous" Nasal script  ??
> >
> > May be any idea which is not coming from you is bad  :)
>
> That's funny. So you have forgotten that the code in terrain.nas
> is basically *my* code? I had posted it as sample code to the list

I was not talking about the idea of the nasal script content. I know that it 
is an idea of Cesar :) giving to Cesar what is owned by Cesar ( is the 
translation of a usual French ).

I am talking  about the idea to get within a property included into FG the  
terrain in order to answer to AI animation request and any other Animation 
with or without FDM, though  with YSAIm we don't have that property.
You know..... YASIm  it is that FDM which can be used with helicopter.
If you don't trust me, look at ...... for instance the bo105 or the S-51... 
Oh by the way S-51 wants for the rescue animation a property with terrain.
>
>  
> http://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg124
>33.html
>
> and you just took it and put it in a loop. But even if it's
> my code, I still think it's just a hack around a missing
> JSBSim feature. I suggest to submit the feature instead.   ;-)
>
> m.
>

Cheers


-- 
Gérard
http://pagesperso-orange.fr/GRTux/

J'ai décidé d'être heureux parce que c'est bon pour la santé. 
Voltaire


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to