Re: [hatari-devel] Hatari debug mode

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]

Eero Tamminen schrieb:
And it works the same when Hatari is build as Windows GUI app (the 
default) or as CLI app (what you do)?

I'm not sure I get the question. Of course, it does not work the same; this is precisely the point why I modify Hatari to be a console application. Perhaps, the following table clears things up:

Neither choice is 100% optimal, but my patch suits my use-case way better.

I guess in general starting applications from console is nowadays really 
rare in Windows, much more so than in Linux [1].  So opening a new 
console window on Windows when needed is not a problem for most people.

Well, I launch Hatari exclusively from the console; hence, I find this separate window unbearably annoying. In particular, the separate window automatically closes when Hatari quits. So, I loose all output, unless I copy-paste it before quitting Hatari. In contrast, when Hatari re-uses my existing console window, I can use its scroll-back buffer, long after Hatari has quit. Then again, I'm tech-savvy enough to just patch the required change into Hatari with a hex editor when I use a release binary.

However, there's the Hatari use-case of redirecting Hatari trace etc 
output to a file.  Will opening of a new console window interrupt that, 
and completely loose rest of the output when the new window is closed at 
Hatari exit?

Right now, "hatari -W" prevents the redirection of Hatari output into a file, because you freopen all the standard handles. With your recent patch, this will now also happen if the user presses AltGr+Pause.

Regards
Christian

-- 
Christian Zietz  -  CHZ-Soft  -  czietz@xxxxxxx
WWW: https://www.chzsoft.de/
New GnuPG-Key-ID: 0x8708B34C827B159E

Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/