Sounds consistent. I'd expect that the compiled BouncingBalls.exe can be
run twice because you get two separate processes, each opening a top-level
window only once. Sadly, this limitation stops wxHaskell from being useful
for exploratory programming, which is why I stopped using it several years
I tried running BouncingBalls.hs in the samples\wxcore directory; inside
GHCi, it runs the second time only for a short while, then crashes. The
Windows application log shows exception code 0xc005, which means
"Access violation". The standalone BouncingBalls.exe can be run multiple
The original bug report (perhaps 7 years ago) was at
http://sourceforge.net/p/wxhaskell/bugs/84/ . Seems to be gone now. The
symptom was a reliable crash whenever a second top-level window was
displayed from a given process, whether in ghci or standalone compiled.
Especially inconvenient with
