From: shelarcy <she...@gm...> - 2008-05-26 08:55:14
|
Hi, I'm sorry about my reply is late. On Thu, 15 May 2008 17:15:54 +0900, Eric Y. Kow <eri...@gm...> wrote: > Shelarcy: any ideas? I found Mad's previous patch left an problem for Windows platform. http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/423 Windows' stdout, stdin and stdout requires console. But we can build wxHaskell GUI program without console by -optl-mwindows option. So, withCharResult's "hPutStrLn stderr" causes problem. I fixed this problem by using Debug.Trace.putTraceMsg instedad of hPutStrLn stderr. http://www.haskell.org/ghc/docs/6.8.2/html/users_guide/terminal-interaction.html http://www.haskell.org/ghc/docs/6.8.2/html/libraries/base/Debug-Trace.html#v%3AputTraceMsg I will send patch soonly (with a few extention). But I don't know this problem is a Brend's problem. Best Regards, > On Thu, May 08, 2008 at 13:10:12 +0200, Bernd Holzmüller wrote: >> I use wxHaskell 0.10.3 on Windows (XP) for writing a GUI to manage and >> execute test cases. Sadly, when using processExecAsyncTimed, the whole >> application sometimes hangs because process termination seems not to be >> recognized reliably. This happens about every 4th or so try. I used >> processExecAsync before which works but is deprecated and slow (because >> we have a byte-wise stdout stream). Any idea whether this is a wxWidgets >> problem or is wxHaskell specific? -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |