Re: [Flightgear-devel] readXML problems

2005-06-30 Thread Erik Hofman
Jon Berndt wrote: The item I see as most suspect now is the "false" result from the call to input.good(). Did you check the file in a browser to make sure it contains valid XML? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.or

RE: [Flightgear-devel] readXML problems

2005-06-30 Thread Jon Berndt
> > void > > readXML (istream &input, XMLVisitor &visitor, const string &path) > > { > > > > engine_filename = FindEngineFullPathname(engine_filename); > > readXML(engine_filename, *engine_file_parser); > > > The parameters don't match up for one thing. "engine_filename" is a string? > > D

Re: [Flightgear-devel] readXML problems

2005-06-30 Thread Dave Culp
> void > readXML (istream &input, XMLVisitor &visitor, const string &path) > { > engine_filename = FindEngineFullPathname(engine_filename); > readXML(engine_filename, *engine_file_parser); The parameters don't match up for one thing. "engine_filename" is a string? Dave __

RE: [Flightgear-devel] readXML problems

2005-06-30 Thread Jon Berndt
> > void > > readXML (istream &input, XMLVisitor &visitor, const string &path) > > { > > XML_Parser parser = XML_ParserCreate(0); > > > ... > > > XML_ParserFree(parser); > > cout << "A-3" << endl; > > > > throw sg_io_exception("Problem reading file", > >

Re: [Flightgear-devel] readXML problems

2005-06-30 Thread Dave Culp
> void > readXML (istream &input, XMLVisitor &visitor, const string &path) > { > XML_Parser parser = XML_ParserCreate(0); > ... > XML_ParserFree(parser); > cout << "A-3" << endl; > > throw sg_io_exception("Problem reading file", > sg_location(path, >

RE: [Flightgear-devel] readXML problems

2005-06-30 Thread Jon Berndt
Here's an update to what I've discovered - hopefully someone can give me a hint on some questions I have. First, I've added some output statements in easyxml.cxx, in this version of the readXML() function: --- -- start -- --- void readXML (istream &input

RE: [Flightgear-devel] readXML problems

2005-06-28 Thread Jon Berndt
Erik: Are you calling readXML while another call to readXML is in progress? Norman: Can't be done unless this other call is in a different thread :-) Jon: > I'm doing it in standalone JSBSim (calling readXML from within another > readXML()). I > thought you simply had to provide new arguments.

RE: [Flightgear-devel] readXML problems

2005-06-28 Thread Jon Berndt
> Norman Vine wrote: > > Erik Hofman writes: > > > >>Are you calling readXML while another call to readXML is in progress? > > > > > > Can't be done unless this other call is in a different thread :-) > > Hmm, that makes sense. I had the detached method of reading XML files > (non-easyXML) in mind

Re: [Flightgear-devel] readXML problems

2005-06-28 Thread Erik Hofman
Norman Vine wrote: Erik Hofman writes: Are you calling readXML while another call to readXML is in progress? Can't be done unless this other call is in a different thread :-) Hmm, that makes sense. I had the detached method of reading XML files (non-easyXML) in mind where you had to do ev

RE: [Flightgear-devel] readXML problems

2005-06-28 Thread Norman Vine
Erik Hofman writes: > > Are you calling readXML while another call to readXML is in progress? Can't be done unless this other call is in a different thread :-) Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.fligh

Re: [Flightgear-devel] readXML problems

2005-06-28 Thread Erik Hofman
Jon Berndt wrote: I'm continuing to install the new JSBSim code. I've run into a strange problem. After I start up FlightGear and begin to parse an aircraft, I'll be humming along just fine until I get to the point where the engine file is specified. When the engine file is specified, i

RE: [Flightgear-devel] readXML problems

2005-06-28 Thread Jon Berndt
> I'm continuing to install the new JSBSim code. I've run into a strange > problem. After I > start up FlightGear and begin to parse an aircraft, I'll be humming along > just fine until > I get to the point where the engine file is specified. When the engine file is specified, > it causes the fil