From: Sebastian K. <sk...@gm...> - 2009-09-04 10:35:03
|
Hello, I've just installed wxhaskell via cabal. But every time i create a timer i get this warning message that looks as follows: "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller should check that we have dynamic events" Everything seems to work just fine if i ignore it. So I'm wondering what the meaning of it is and how to get rid of it? The simplest program I've been able to make that produces this message is gui = do f <- frame [text := "Hello World"] t <- timer f [interval := 20] return () If i comment out the timer part i don't get the warning message. Likewise if I modify the program and add an "on paint" event to the frame the warning message never pops up. Like so: gui = do f <- frame [text := "Hello World", on paint := (\_ _ -> return ())] t <- timer f [interval := 20] return () Regards Sebastian Klüft sk...@gm... |
From: Eric Y. K. <eri...@gm...> - 2009-09-04 13:18:31
|
Hi Sebastian, On Fri, Sep 04, 2009 at 12:34:32 +0200, Sebastian Klüft wrote: > "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller > should check that we have dynamic events" > > Everything seems to work just fine if i ignore it. So I'm wondering > what the meaning of it is and how to get rid of it? I don't really know how to answer your question, but I can at least report that this program does not spit out any error messages: import Graphics.UI.WX main = start gui gui = do f <- frame [text := "Hello World"] t <- timer f [interval := 20] return () Works for me on MacOS X Leopard without any warnings. I'm using a wxWidgets I built myself. Maybe folks on other platforms could try the same? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-04 21:06:48
|
Thanks for the reply. I can add that I'm also running Mac OS X Leopard and I installed WXHaskell through Cabal. GHC version: 6.10.4. -- Sebastian Klüft sk...@gm... 2009/9/4 Eric Y. Kow <eri...@gm...>: > Hi Sebastian, > > On Fri, Sep 04, 2009 at 12:34:32 +0200, Sebastian Klüft wrote: >> "assert "m_dynamicEvents" failed in SearchDynamicEventTable(): caller >> should check that we have dynamic events" >> >> Everything seems to work just fine if i ignore it. So I'm wondering >> what the meaning of it is and how to get rid of it? > > I don't really know how to answer your question, but I can at least > report that this program does not spit out any error messages: > > import Graphics.UI.WX > > main = start gui > gui = do > f <- frame [text := "Hello World"] > t <- timer f [interval := 20] > return () > > Works for me on MacOS X Leopard without any warnings. > I'm using a wxWidgets I built myself. > > Maybe folks on other platforms could try the same? > > -- > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > PGP Key ID: 08AC04F9 > |
From: Eric Y. K. <eri...@gm...> - 2009-09-05 09:11:01
|
On Fri, Sep 04, 2009 at 23:06:18 +0200, Sebastian Klüft wrote: > I can add that I'm also running Mac OS X Leopard and I installed > WXHaskell through Cabal. Hmm, that's interesting. Are you using the stock wxWidgets or one that you built yourself? Also, I'm using the new recabalised wxcore (which has the advantage that you don't need to install it in the global package space), if it makes a difference. > GHC version: 6.10.4. Likewise. Latest Haskell Platform. Eric PS. What would make me very happy is if magically, the wxWidgets that ships with Snow Leopard just works with wxHaskell. I'm slightly less grumpy about this now that I've discovered that Ubuntu Jaunty's wxWidgets works just fine. I wonder what's changed where. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-06 19:03:59
|
2009/9/5 Eric Y. Kow <eri...@gm...>: > Hmm, that's interesting. Are you using the stock wxWidgets or one that > you built yourself? Yes I have (sort of). I have installed wxWidgets through MacPorts, so it's built on this machine but everything is done automagically. Guess i could try the binary distribution instead and see if that helps. > Also, I'm using the new recabalised wxcore (which has the advantage that > you don't need to install it in the global package space), if it makes a > difference. How do I get this "recabalised" wxcore? /Sebastian |
From: Eric Y. K. <eri...@gm...> - 2009-09-06 19:14:34
|
On Sun, Sep 06, 2009 at 21:03:27 +0200, Sebastian Klüft wrote: > How do I get this "recabalised" wxcore? git clone git://github.com/bsl/wxdirect git clone git://github.com/bsl/wxcore It's not yet officially supported by the wxHaskell team, but perhaps in the future it will be. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric Y. K. <eri...@gm...> - 2009-09-07 08:53:57
|
On Sun, Sep 06, 2009 at 21:03:27 +0200, Sebastian Klüft wrote: > > Hmm, that's interesting. Are you using the stock wxWidgets or one that > > you built yourself? > > Yes I have (sort of). I have installed wxWidgets through MacPorts, so > it's built on this machine but everything is done automagically. Another thought: are you sure it's your MacPorts-installed wxWidgets that's being picked up by the wxcore configure script and not the stock one? Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Sebastian K. <sk...@gm...> - 2009-09-09 08:33:31
|
2009/9/7 Eric Y. Kow <eri...@gm...>: > Another thought: are you sure it's your MacPorts-installed wxWidgets > that's being picked up by the wxcore configure script and not the stock > one? You might be right about this. Because i rebuilt wxHaskell again now to check if it uses the right version of wxWidgets, and it didn't. So i reinstalled wxWidgets and then built wxHaskell again and now it works! Thanks for all the help Sebastian |