[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Flightplan call settings handlers

From: Christophe De Wagter
Subject: Re: [Paparazzi-devel] Flightplan call settings handlers
Date: Sun, 18 May 2014 14:03:25 +0200

Hi Gautier,

Thanks. That is what I had for heading in the end, but for flight_altitude I still needed the { ...; FALSE; } trick. 


#define SetHeading(x) {navigation_SetNavHeading((x));FALSE;}
#define SetFlightAltitude(x) {navigation_SetFlightAltitude((x));FALSE;}

to navigation.h? (and wiki)


On Sun, May 18, 2014 at 10:36 AM, Gautier Hattenberger <address@hidden> wrote:
<set var="nav_heading" value="ANGLE_BFP_OF_REAL(RadOfDeg(180))"/>

a bit long but no dummy variables, nor changes.

Since the return value of the settings handler is not important, we could also change them to return FALSE so they can be used in flight plan call instruction as well.


Le 18/05/2014 09:43, Christophe De Wagter a écrit :
How can the flightplan call "handlers" as used in settings?

E.g. navigation_SetNavHeading(x) 

<set var="dummy" value="navigation_SetNavHeading(180)" /> needs an ugly dummy.

<call fun="navigation_SetNavHeading(180)" /> does never return as the settings handler does not return FALSE when ready.

<call fun="{navigation_SetNavHeading(180); FALSE; }" /> seems to work, but feels like a weird hack. 

Is there another solution that I missed?


Paparazzi-devel mailing list

Paparazzi-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]