Hi,
On Wednesday 16 August 2006 11:12, Durk Talsma wrote:
> Okay,looks like I found it: Because I'm pushing back one route id less than
> I'm pushing back waypoint identifiers, I should also make sure that I'm not
> popping back the route id in the final exit of trace. Fix should be in CVS
> in a
On Sunday 13 August 2006 21:34, Mathias Fröhlich wrote:
> Hi Durk,
>
> On Saturday 12 August 2006 00:32, Durk Talsma wrote:
> > Btw, where did you experience these problems (which airport), and how did
> > they manifest themselves? Program crashes? I've been running recent
> > versions of FlightGea
Hi Durk,
On Saturday 12 August 2006 00:32, Durk Talsma wrote:
> Btw, where did you experience these problems (which airport), and how did
> they manifest themselves? Program crashes? I've been running recent
> versions of FlightGear using the EHAM groundnetwork, and hadn't seen any
> problem yet.
On Friday 11 August 2006 23:43, Mathias Fröhlich wrote:
> Hi,
>
> while debugging Maik's multiplayer problems, Olaf and I experienced some
> problems in groudnetwork.cxx.
>
> At the end of the FGGroundNetwork::trance() there are two pop_back's where
> the second one poped an non existent last entry
Hi,
while debugging Maik's multiplayer problems, Olaf and I experienced some
problems in groudnetwork.cxx.
At the end of the FGGroundNetwork::trance() there are two pop_back's where the
second one poped an non existent last entry from the routesStack vector.
We tried to avoid poping in that ca
5 matches
Mail list logo
