Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
On vendredi 10 octobre 2008, Alexis Bory - xiii wrote:
> > > $ grep launch src/MultiPlayer/multiplaymgr.cxx {107,
> > > "gear/launchbar/position-norm", SGPropertyNode::FLOAT}, {108,
> > > "gear/launchbar/state", SGPropertyNode::STRING}, {109,
> > > "gear/launchbar/holdback-position-norm", SGPropertyNode::FLOAT},
> >
> > That should have been "we". I've no idea how it got into the list of
> > properties. And I agree "we" don't need it. I don't recall any
> > discussion about it, but I would recommend it removal.
>
> This could be used for some "on deck animations"... but I don't know
> who is going to model the cat officer dance...
>
> Alexis
>
Why not :),
Out of that specific talk.
There is an other animation to be done ( i have not finished it) , is the
LSO animation witch should come with the straight deck Carrier Arromanches.
--
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
On vendredi 10 octobre 2008, Melchior FRANZ wrote:
> * gerard robin -- Friday 10 October 2008:
> > So from the boolean value coming from JSBSim i have to listen it,
> > and to convert with a specific Nasal script , which is tricky.
>
> You are slightly overrating the trickiness factor ... :-}
>
> setlistener("/gear/launchbar/state", func(n) {
> setprop("/fdm/jsbsim/launchbar/launch-bar-state", n.getValue() ==
> "Engaged"); });
>
> But I agree with you. I've never liked the wasteful string
> transmission over MP(!), and I've criticized that before.
> But I don't know if changing the MP property is "allowed".
> I guess we'd also have to change the id number, and leave
> the old one (108) unused.
>
> m.
>
No overrating at all (rather underrating, like the economic financial rate
today :) :) )
My Nasal script is old fashion ( from 2006 )
JBD_op=func{
if(getprop("/fdm/jsbsim/launchbar/launch-bar-state")== 1){
setprop("/gear/launchbar/state","Engaged");
# print("Engaged");
}else{setprop("/gear/launchbar/state","Disengaged");
}
}
setlistener("/fdm/jsbsim/launchbar/launch-bar-state",JBD_op);
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
On vendredi 10 octobre 2008, Vivian Meazza wrote: > gerard robin wrote > > > A question, may be to Vivian. > > > > About one carrier feature /gear/launchbar/state which is > > wanted by > > the JBD animation. > > i wonder if it won't be possible to replace the text constant value > > "Engaged" > > with a boolean value, into the carrier program ? > > > > Working with JSBSIm FDM which don't like text constant value, it is > > unable > > to process it. > > So from the boolean value coming from JSBSim i have to listen it, and > > to > > convert with a specific Nasal script , which is tricky. > > ===> > > from > > /fdm/jsbsim/launchbar/launch-bar-state ( 1 or 0 ) > > to > > /gear/launchbar/state (Engaged or Disengaged) > > < > > > > This only necessary for animation, nothing else :) > > YASim launchbar status is "Engaged"/"Launching"/"Completed"/"Disengaged" so > I don't think a change to Bool is trivial. YASim does use the status. > However a nasal listener is simple and quick to implement. Don't see a > problem with that as a solution, particularly as it is only for animation. > > Vivian Hello, Vivian, Do i must understand that carrier features is for YASim only, any other FDM having the eye for crying. Do we have to repeat again the past time ( AAR with JSBSim was broken in order to answer to the YASIm request ) ? Won't it be better to have a generic answer Numeric instead of text value? To me everything is possible with JSBSim, but to be able to give to the Carrier JBD the right information => On or Off through a 'Text Value'. This is not MP only a specific AI animation. More seriously i don't mind with it, if it is right for YASim.. let us to go on with the life.:) 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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
Melchior FRANZ > > * Vivian Meazza -- Friday 10 October 2008: > > I've no idea how it got into the list of properties. > > Maybe it's for the (steerable) carrier "aircraft"? Using > 8 bytes more over MP than required is probably not such a > big issue. Demanding string comparisons for every check > is a bit annoying, even though mainly because of the ugly > capitalization. :-} > I really can't think what it might be useful for in that context, but it's not in cvs AFAIKS, so I can't check. I hope that we can come up with a better solution than the carrier "aircraft" in the fullness of time. Petr Gotthard's patch might have potential in that respect. I hope that we can investigate that a bit more. Vivian - 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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
* Vivian Meazza -- Friday 10 October 2008: > I've no idea how it got into the list of properties. Maybe it's for the (steerable) carrier "aircraft"? Using 8 bytes more over MP than required is probably not such a big issue. Demanding string comparisons for every check is a bit annoying, even though mainly because of the ugly capitalization. :-} m. - 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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
> > $ grep launch src/MultiPlayer/multiplaymgr.cxx {107,
> > "gear/launchbar/position-norm", SGPropertyNode::FLOAT}, {108,
> > "gear/launchbar/state", SGPropertyNode::STRING}, {109,
> > "gear/launchbar/holdback-position-norm", SGPropertyNode::FLOAT},
> >
>
> That should have been "we". I've no idea how it got into the list of
> properties. And I agree "we" don't need it. I don't recall any
> discussion about it, but I would recommend it removal.
This could be used for some "on deck animations"... but I don't know
who is going to model the cat officer dance...
Alexis
-
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
: Melchior FRANZ
> * Vivian Meazza -- Friday 10 October 2008:
> > You need to pass the launchbar state over mp?
>
> The "you" is inappropriate. I didn't say that I need it,
> and I didn't add it to the transmitted properties. Yet
> it is there! Why don't you read the source?!
>
> $ grep launch src/MultiPlayer/multiplaymgr.cxx
>{107, "gear/launchbar/position-norm",
> SGPropertyNode::FLOAT},
>{108, "gear/launchbar/state",
> SGPropertyNode::STRING},
>{109, "gear/launchbar/holdback-position-norm",
> SGPropertyNode::FLOAT},
>
That should have been "we". I've no idea how it got into the list of
properties. And I agree "we" don't need it. I don't recall any discussion
about it, but I would recommend it removal.
Vivian
-
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
* Vivian Meazza -- Friday 10 October 2008:
> You need to pass the launchbar state over mp?
The "you" is inappropriate. I didn't say that I need it,
and I didn't add it to the transmitted properties. Yet
it is there! Why don't you read the source?!
$ grep launch src/MultiPlayer/multiplaymgr.cxx
{107, "gear/launchbar/position-norm", SGPropertyNode::FLOAT},
{108, "gear/launchbar/state", SGPropertyNode::STRING},
{109, "gear/launchbar/holdback-position-norm",SGPropertyNode::FLOAT},
m.
-
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
Melchior FRANZ
> Better make that ...
>
> setlistener("/gear/launchbar/state", func(n) {
> setprop("/fdm/jsbsim/launchbar/launch-bar-state", n.getValue() ==
> "Engaged");
> }, 0, 0);
>
> ... because I seem to remember that the property is written to
> quite frequently (also a bug, if you ask me), and the second
> 0 makes sure that the listener function is only triggered
> when the property value actually changed. Trickier now! :-)
>
You need to pass the launchbar state over mp? The property is exposed so
that you can see what you are doing when you are trying to engage the cat.
Surely it's launchbar position that needs to be on mp?
Vivian
-
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
Better make that ...
setlistener("/gear/launchbar/state", func(n) {
setprop("/fdm/jsbsim/launchbar/launch-bar-state", n.getValue() ==
"Engaged");
}, 0, 0);
... because I seem to remember that the property is written to
quite frequently (also a bug, if you ask me), and the second
0 makes sure that the listener function is only triggered
when the property value actually changed. Trickier now! :-)
m.
-
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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
gerard robin wrote > A question, may be to Vivian. > > About one carrier feature /gear/launchbar/state which is wanted > by > the JBD animation. > i wonder if it won't be possible to replace the text constant value > "Engaged" > with a boolean value, into the carrier program ? > > Working with JSBSIm FDM which don't like text constant value, it is > unable > to process it. > So from the boolean value coming from JSBSim i have to listen it, and > to > convert with a specific Nasal script , which is tricky. > ===> > from > /fdm/jsbsim/launchbar/launch-bar-state ( 1 or 0 ) > to > /gear/launchbar/state (Engaged or Disengaged) > < > > This only necessary for animation, nothing else :) > YASim launchbar status is "Engaged"/"Launching"/"Completed"/"Disengaged" so I don't think a change to Bool is trivial. YASim does use the status. However a nasal listener is simple and quick to implement. Don't see a problem with that as a solution, particularly as it is only for animation. Vivian - 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
Re: [Flightgear-devel] about /gear/launchbar/state","Engaged"
* gerard robin -- Friday 10 October 2008:
> So from the boolean value coming from JSBSim i have to listen it,
> and to convert with a specific Nasal script , which is tricky.
You are slightly overrating the trickiness factor ... :-}
setlistener("/gear/launchbar/state", func(n) {
setprop("/fdm/jsbsim/launchbar/launch-bar-state", n.getValue() ==
"Engaged");
});
But I agree with you. I've never liked the wasteful string
transmission over MP(!), and I've criticized that before.
But I don't know if changing the MP property is "allowed".
I guess we'd also have to change the id number, and leave
the old one (108) unused.
m.
-
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
