Hi Eric,
Am I correct in recalling that you did some of the work to get wxHaskell
supporting unicode?
I've using wxHaskell with wxWidgets 2.9.2 (the latest development release)
and it seems that any attempt to get back a wxString in Haskell code will
result in a "Prelude.chr: bad argument:" crash at run time; I've verified
that the same code works correctly with wxWidgets 2.8.
A good example is ./samples/wx/ListCtrl.hs, you will get the crash when you
click on an item in the list.
Now the good news is that this is almost certainly related to the changes to
unicode handling in wxWidgets:
http://docs.wxwidgets.org/2.9/overview_changes_since28.html
But I thought I'd send out a message asking for a sanity check before I get
too busy working on fixing it.
Dave,
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
