Norman Vine writes:
> Right !
> You need to trace the source and for this there is no substitute for an
> editor that has a 'ctags' equivalant builtin with 'jump to declaration' and
> 'jump to definition' functions
>
> http://ctags.sourceforge.net/
>
> extending this concept to the 'pr
David Megginson writes:
>
> Norman Vine writes:
>
> > > I think that's a great idea, as long as we recognize that it will be
> > > perpetually a work in progress.
> >
> > In what way is this any different then the 'C' code ??
>
> Not much, but you'll notice how few of the C++ interfaces are
>
Norman Vine writes:
> > I think that's a great idea, as long as we recognize that it will be
> > perpetually a work in progress.
>
> In what way is this any different then the 'C' code ??
Not much, but you'll notice how few of the C++ interfaces are
documented.
Stuff like JavaDoc/doc++/dox
David Megginson
> Norman Vine writes:
>
> > But there are many "Fixed Lists" of properties for example
> >
> > PitotSystem::init ()
> > {
> > _serviceable_node = fgGetNode("/systems/pitot[0]/serviceable",
true);
> > _pressure_node = fgGetNode("/environment/pressure-inhg", true);
>
Norman Vine writes:
> But there are many "Fixed Lists" of properties for example
>
> PitotSystem::init ()
> {
> _serviceable_node = fgGetNode("/systems/pitot[0]/serviceable", true);
> _pressure_node = fgGetNode("/environment/pressure-inhg", true);
> _density_node = fgGetNode(
Moved from flightgear-users
David Megginson writes
> Mark Fisher writes:
>
> > Again, I'm looking for the location of the dictionary of permissible
> > properties that can be set using the .XML joystick files, and their
> > permissible value ranges.
>
> Take a look at the property browser
