This may sound like a lame idea. I am not all that versed on xml
technology,
but it seems to me that there is a standard form for something
like this. In
the database world there is something called a Data dictionary
that works as
a central repository for data items, their types, default
Jon Berndt [EMAIL PROTECTED] said:
This may sound like a lame idea. I am not all that versed on xml
technology,
but it seems to me that there is a standard form for something
like this. In
the database world there is something called a Data dictionary
that works as
a central
Norman Vine writes:
Question:
Is there any reason that ALL of the joysticks from the config files are
represented in the 'resident' property tree ??
It's on my TODO list, but it someone else wants to take that over I'll
be very happy.
All the best,
David
--
David Megginson, [EMAIL
Michael Bonar writes:
MSVC6 has a Visio add-on that allows you to reverse engineer C code
into UML diagrams. Anybody have experience with it? I was
thinking of giving that a try to see what it looks like. In the
meantime, I will see what I can find on code documentation.
Many of the
Norman Vine writes:
Thanks. That's pretty handy. I notice that this does not seem
to include all of the property information in some files, eg
sound.xml (and several other .xml files seen when searching
through the props file).
Yes I noticed that this is not a *complete* dump
Jim Wilson writes:
Is there a way to copy a block of properties (ie an equivelent to
cp -ax dir1 dir2)? IIRC this was discussed at one time, and I'm
wondering if it has been implemented yet.
See simgear/misc/props_io:
/**
* Copy properties from one node to another.
*/
bool
Jim Wilson writes:
Is this the sort of thing that a standard DTD document provides?
Or could we develop our own dictionary of sorts? I'm suggesting
that this could provide the documentation we need (if it is
centralized).
No, DTDs are strictly structural -- think of it as a specialized
Norman Vine writes:
Jim Wilson writes:
Is there a way to copy a block of properties
#include simgear/misc/props_io.hxx
copyProperties (const SGPropertyNode *in, SGPropertyNode *out)
But AFAIK this requires that the 'out' nodes exist
i.e. this copies but does not construct
David Megginson wrote:
[EMAIL PROTECTED] writes:
FWIW, I found 1 a bit quiet, although audiable over the idling engine, so I
set it to 2, which was audiable over the full throttle engine. Thats on
windows though, although I could certainly make it out over the idling engine
when I
Erik Hofman writes:
This might be a driver issue (either kernel or plib). It sounds like
your volume scales linear instead of logarithmic ...
That's a reasonable guess. What would the next step be?
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
David Megginson wrote:
Erik Hofman writes:
This might be a driver issue (either kernel or plib). It sounds like
your volume scales linear instead of logarithmic ...
That's a reasonable guess. What would the next step be?
What kernel driver do you use: OSS or ALSA?
And which hardware?
David Megginson writes:
Norman Vine writes:
Thanks. That's pretty handy. I notice that this does not seem
to include all of the property information in some files, eg
sound.xml (and several other .xml files seen when searching
through the props file).
Yes I noticed
Hi,
I'm just looking for a few pointers to start off. I see that the DIS
interface has been mentioned as a 'would like to have' feature. I
have had a quick look at the code and I guess the interface would be
similar, in a way, to the net_send.cxx code for the OLK stuff, in
that it receives
Doxygen would need to be tweaked a bit, since it is not set up for XML I
started hunting for an XML documentation engine last night. All the ones I
have found so far do only one page at a time. We want it to do the same
thing that Doxygen does, which is to read through all the
They are very helpful, and that's why the first test of Doxygen turned up such
good results IMHO. If it's decided that this is the way to go, then a simple
code documentation standard would need to be applied to the source to pull
out the information we think is valuable.
Cheers,
Mike
On
Doxygen would need to be tweaked a bit, since it is not set up for XML
I
Right. I was looking at it from another angle. That is, from the source
code side. JSBSim uses properties and in the header we can probably
document all the properties for a particular class. When Doxygen builds
the docs
Erik Hofman writes:
What kernel driver do you use: OSS or ALSA?
OSS (kernel 2.4.20).
And which hardware?
Maestro3.
Thanks, and all the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
___
Flightgear-devel
Norman Vine writes:
I see that but I thought one of the motivating factors for the
'properties' was to have a central location for all of the 'data'
There are different kinds of data. The property tree is meant to
represent the shared state of the program; when a subsystem happens to
use an
Jon Berndt writes:
Right. I was looking at it from another angle. That is, from the source
code side. JSBSim uses properties and in the header we can probably
document all the properties for a particular class. When Doxygen builds
the docs from header comments, those will be included.
David Megginson wrote:
Erik Hofman writes:
What kernel driver do you use: OSS or ALSA?
OSS (kernel 2.4.20).
And which hardware?
Maestro3.
Hmm, according to this article the OSS drivers for the Meastr3 had
problems on a Dell Latitude C800, but it is fairly old (speaking about
Linux
David Megginson wrote:
Erik Hofman writes:
What kernel driver do you use: OSS or ALSA?
OSS (kernel 2.4.20).
And which hardware?
Maestro3.
Article:
http://www.zabbo.net/pipermail/maestro-users/2001-August/000433.html
Erik
___
Erik Hofman writes:
Hmm, according to this article the OSS drivers for the Meastr3 had
problems on a Dell Latitude C800, but it is fairly old (speaking about
Linux 2.4.9).
The article suggests that the maestro3 driver uses a lookup table.
The thing is, I'm not having problems with the
David Megginson wrote:
Erik Hofman writes:
Hmm, according to this article the OSS drivers for the Meastr3 had
problems on a Dell Latitude C800, but it is fairly old (speaking about
Linux 2.4.9).
The article suggests that the maestro3 driver uses a lookup table.
The thing is, I'm not
Erik Hofman writes:
Another question, do you use esd or something like that?
No -- I keep it disabled (or else FlightGear wouldn't work at all).
It could well be that my driver is using linear volume, but then
wouldn't the other relative volumes for FlightGear be wrong as well?
All the
David Megginson wrote:
Erik Hofman writes:
Another question, do you use esd or something like that?
No -- I keep it disabled (or else FlightGear wouldn't work at all).
It could well be that my driver is using linear volume, but then
wouldn't the other relative volumes for FlightGear be wrong
David Megginson wrote:
Erik Hofman writes:
Yes, but like I said, it's hard to know unless you are aware of wha
you're looking for. The mixer volume *sounds* linear to you?
If so, then it's actually logarithmic.
Yes, as far as I can tell, it sounds linear.
You are not making it easy for
Erik Hofman writes:
You are not making it easy for me ...
To be honnest, I can't think of an explaination anymore.
OK, as long as no one else is reporting the same problem, we can leave
it for now.
Thanks,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
David Megginson wrote:
Erik Hofman writes:
You are not making it easy for me ...
To be honnest, I can't think of an explaination anymore.
OK, as long as no one else is reporting the same problem, we can leave
it for now.
Just one more thing:
Make sure bass and treble aren't amplified in
Erik Hofman writes:
You are not making it easy for me ...
To be honnest, I can't think of an explaination anymore.
OK, as long as no one else is reporting the same problem, we can leave
it for now.
Just one more thing:
Make sure bass and treble aren't amplified in the
On Monday, December 23, 2002, at 02:14 pm, David Megginson wrote:
Hmm. I wonder what the issue is. At 10, I can hear, perhaps, 75% of
it over the idling engine, but I still have to strain to make it out.
I don't know enough about the audio side to troubleshoot this easily.
I would just
James Turner writes:
I would just like to corroborate David's results, I thought ATC was
broken until I realized I could *just* hear it over the engine noise.
This is on Linux with ALSA, all the other FG sounds have a 'normal'
volume.
So we're seeing the problem with both ALSA and
Here is a patch that allows assignment from one property in the tree to another
property. Also put a check in there so that FG no longer segfaults if the
value to be assigned is not defined in the XML.
Usage Example:
commandproperty-assign/command
32 matches
Mail list logo
