On Thursday 28 September 2006 18:43, Geoff Air wrote:
>
> PS: I have sometimes wondered where the AI planes
> go, and was 'startled' to find that after chasing
> one in the UFO - giving the passengers something
> to talk about - it simply 'disappears' after reaching
> about 27,000 feet, maybe 10 m
Hi Fred,
>http://cvs.flightgear.org/cgi-bin/viewvc/viewvc.cgi/source/simgear/debug/logstream.hxx?annotate=1.9&root=SimGear-0.3
Wow, thank you for this pointer ... what a fantastic
colour coded 'historic' view you get of the file,
ANY file ... I will now REMEMBER this http access ...
and then view
Quoting Geoff Air:
> In MSVC8, only NOW do I note you have REMOVED the
> _CONSOLE subsystem define, and put _WINDOWS into
> the MSVC8 'solution' file ...
I don't switch to MSVC8 yet. These files are not from me.
You only have to change the link option. The presence of both WinMain and main
makes
Selon Geoff Air :
> Perhaps the author of this code could give us some
> of the reasoning of why this was added, under a
> _MSC_VER flag ...
>
> Maybe there is a way to 'explore' this in cvs,
> but I will need some help with the cvs commands to get
> at this 'historic' information ... like when wa
Hi Geoff
Geoff Air schrieb:
> I really WISH there was a way to re-direct this output
> to a disk FILE, so the whole output could be reviewed,
> but I have tried, and tried, with simgear logging, but
> have never quite succeeded ... I know, it should be
> 'simple' ;=))
> ...
> logbuf::overflow( int
Hi Maek,
Sorry for the longish post ...
>Therefore I added
>#ifdef _MSC_VER
>cerr << "Hit a key to continue..." << endl;
>cin.get();
>#endif
>to function
>void fgExitCleanup()
Thank you for bringing this up! ... it has been a problem
for a long, LONG TIME ... IIRC there was a tim
Selon Reagan Thomas :
> Frederic Bouvier wrote:
> > Selon Maik Justus :
> >
> >
> >>Hi,
> >>
> >>on windows flightgear open a extra console window for the text output.
> >>When flightgear ends this window is closed regardless if there is any
> >>info the user might want to read (e. g. error messag
Hello Fred, Hello Reagan,
thank you very much for your prompt help.
@Reagan
Maybe the "broken pipe" is due to the console window generated by
flightgear? Maybe flightgear really closes your pipe!
Frederic Bouvier wrote:
> Hi Maik,
>
> if you start fgfs with fgrun, fgfs output its messages in th
Frederic Bouvier wrote:
> Selon Maik Justus :
>
>
>>Hi,
>>
>>on windows flightgear open a extra console window for the text output.
>>When flightgear ends this window is closed regardless if there is any
>>info the user might want to read (e. g. error messages of the xml
>>parser). On windows you
Selon Maik Justus :
> Hi,
>
> on windows flightgear open a extra console window for the text output.
> When flightgear ends this window is closed regardless if there is any
> info the user might want to read (e. g. error messages of the xml
> parser). On windows you can not write thies messages to
Maik Justus wrote:
>Hi,
>
>on windows flightgear open a extra console window for the text output.
>When flightgear ends this window is closed regardless if there is any
>info the user might want to read (e. g. error messages of the xml
>parser). On windows you can not write thies messages to a
11 matches
Mail list logo
