Carsten Hoefer wrote:
BTW: How do I play sounds by Nasal scripts?
The same way one would do animations using Nasal;
Adjust properties in Nasal (they may be private properties in your own
subtree of the property list, say /tmp/aircraft) and let the sound
configuration file act on those
Andy Ross schrieb:
Steve Knoblock wrote:
1. Will Nasal scripting give me all options to program the
push-back function (incl. playing sound files and checking
distances to other planes or to next taxi way)?
I am not sure of this, but NASAL can listen for properties and then
On Tue, 29 Nov 2005 05:57:53 -0600, you wrote:
or just haven't gotten around to. Wiring up property/command
interfaces for C++ subsystems is generally pretty easy.
Andy
Is there a list of all properties or commands available or how do I find
the appropriate functions?
I allready found the
Steve Knoblock wrote:
1. Will Nasal scripting give me all options to program the
push-back function (incl. playing sound files and checking
distances to other planes or to next taxi way)?
I am not sure of this, but NASAL can listen for properties and then
change properties,
Yes, Nasal
Andy Ross schrieb:
Steve Knoblock wrote:
1. Will Nasal scripting give me all options to program the
push-back function (incl. playing sound files and checking
distances to other planes or to next taxi way)?
I am not sure of this, but NASAL can listen for properties and then
Melchior FRANZ wrote:
Wouldn't work in my case. Would only make it even less
elegant. Then I better stick with this:
Only if you don't want to write your own functions (in which case
every feature I don't want to support is going to be inelegant
and you'll never win until I turn Nasal into
I wrote:
Write a function to [...]. Compose them appropriately to set bits
in numbers. Probably four lines of code,
Turns out it's three lines of code:
n2s = func(n) { var s = buf(6); setfld(s, 0, 48, n); return s; }
getbit = func(n, b) { getfld(var s = n2s(n), b, 1) }
setbit = func(n,
Melchior FRANZ wrote:
Alternatively, take TeX's syntax: `\A ... for extra geek points. ;-)
If you are really seeking for ggek points:
$eq1 = 2 * $val;
$eq2 = -7 + $val;
test_val = (1 (3 + #-3 * ${want_eq1 ? $eq1 : $eq2});
:-)
Erik
___
Melchior FRANZ
* Vivian Meazza -- Sunday 24 April 2005 20:41:
Andy Ross wrote
`A` @A $A %A A @A $A %A A cA
Anything but `A` - I'm bound to misread that in the future sometime. I
favour a function.
Hmm ... and I changed my mind and would now find `A` a
Melchior,
That was exactly what I needed
Thanks,
Vance
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Melchior FRANZ
Sent: Friday, November 19, 2004 12:05 PM
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] Re: Nasal
* Vance Souders -- Friday 19
Andy Ross wrote:
But here's a question on a related subject. How do we handle
declaration of Nasal code? The ability to write inline handlers is
great, but limited to small functions. The ability to drop module
files into the Nasal directory is great too, for globally useful
code.
But
Melchior FRANZ wrote:
This and your examples (mouse handling, etc.) have totally
won me over! I've already written my first nasal script
I haven't had time to play with NASAL yet, but now that it's integrated and
people seem to like it, it's probably time to start refactoring FlightGear a
bit.
David Megginson wrote:
Originally, I defined actions using XML mainly because we didn't have
a scripting language, but ideally, we should share up the labour like
this:
XML = declarative
NASAL = imperative
Completely agree. Although it should be pointed out that there's
significant gray
13 matches
Mail list logo
