You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(12) |
Aug
(34) |
Sep
(14) |
Oct
(36) |
Nov
(32) |
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(9) |
Mar
(31) |
Apr
(36) |
May
(17) |
Jun
(21) |
Jul
(13) |
Aug
(18) |
Sep
(2) |
Oct
(10) |
Nov
(18) |
Dec
(28) |
2005 |
Jan
(26) |
Feb
(15) |
Mar
(26) |
Apr
(11) |
May
(60) |
Jun
(3) |
Jul
(12) |
Aug
(4) |
Sep
(12) |
Oct
(19) |
Nov
(36) |
Dec
(10) |
2006 |
Jan
(6) |
Feb
(13) |
Mar
(6) |
Apr
(2) |
May
(9) |
Jun
(3) |
Jul
(6) |
Aug
(13) |
Sep
(1) |
Oct
(24) |
Nov
(33) |
Dec
(47) |
2007 |
Jan
(21) |
Feb
(41) |
Mar
(17) |
Apr
(9) |
May
(4) |
Jun
(20) |
Jul
(24) |
Aug
(71) |
Sep
(35) |
Oct
(10) |
Nov
(39) |
Dec
(39) |
2008 |
Jan
(24) |
Feb
(42) |
Mar
(61) |
Apr
(12) |
May
(11) |
Jun
(4) |
Jul
(9) |
Aug
(6) |
Sep
(6) |
Oct
(4) |
Nov
(3) |
Dec
(14) |
2009 |
Jan
(25) |
Feb
(18) |
Mar
(19) |
Apr
(24) |
May
(14) |
Jun
(7) |
Jul
(14) |
Aug
(25) |
Sep
(40) |
Oct
(20) |
Nov
(22) |
Dec
(4) |
2010 |
Jan
(55) |
Feb
(11) |
Mar
(9) |
Apr
(10) |
May
(10) |
Jun
(9) |
Jul
(7) |
Aug
(4) |
Sep
(15) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
2011 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
(6) |
May
(20) |
Jun
(30) |
Jul
(15) |
Aug
(4) |
Sep
(23) |
Oct
(24) |
Nov
(3) |
Dec
(8) |
2012 |
Jan
(23) |
Feb
(7) |
Mar
(19) |
Apr
(48) |
May
(8) |
Jun
(27) |
Jul
(10) |
Aug
(1) |
Sep
(11) |
Oct
(1) |
Nov
|
Dec
(3) |
2013 |
Jan
(1) |
Feb
|
Mar
(17) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2015 |
Jan
|
Feb
|
Mar
(14) |
Apr
(5) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(5) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
2016 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Henk-Jan v. T. <hj...@ch...> - 2009-01-23 22:30:26
|
On Thu, 22 Jan 2009 13:11:15 +0100, Günther Schmidt <re...@fe...> wrote: > Hi, > > I have a ridiculously trivial problem, I can't seem to get creating a > bitmap button right with 3 images for the different states, active, > pressed, and inactive. > > It just draws an "empty" space for the button on screen. > > Günther > Maybe it is an image format that cannot be handled properly? Can you show us the code you use? I have attached a program that switches between three images for the button, each time the button is clicked. -- Regards, Henk-Jan van Tuyl -- http://functor.bamikanarie.com http://Van.Tuyl.eu/ -- |
From: Günther S. <re...@fe...> - 2009-01-22 13:05:10
|
Hi, I have a ridiculously trivial problem, I can't seem to get creating a bitmap button right with 3 images for the different states, active, pressed, and inactive. It just draws an "empty" space for the button on screen. Günther |
From: Jeroen J. <Jer...@ug...> - 2009-01-14 22:44:27
|
Hi Mads, I am running version 2.12.9-3ubuntu. Kind regards, Jeroen. On Wednesday 14 January 2009 23:13:56 Mads Lindstrøm wrote: > Hi Jeroen Janssen: > > Which version of libgtk are you running? > > /Mads > > > Follow-up: > > > > With latest darcs version, showing revision 0.11.1 this time, this error > > does not occur any longer. However, wxhaskell is still not working as > > now programs fail with: > > > > (process:3353): GLib-GObject-CRITICAL > > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > > `initialization_value != 0' failed > > > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed > > > > This happens for the example I mentioned in my previous e-mail but also > > for the examples included with wxhaskell (BoxedCombinator etc). > > > > Any help with this? The parameters stayed the same as in my previous > > e-mail (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even tried > > updating to wxwidgets 2.8.9, but to no avail, same error. > > I build wxhaskell with "cabal" install, followed by the cd wx en usual > > build process if that may be of any help. > > > > Kind regards, > > > > On Tuesday 06 January 2009 19:27:32 Jeroen Janssen wrote: > > > Hi, > > > > > > I tried compiling this program: > > > > > > module Main where > > > > > > import Graphics.UI.WX > > > > > > main :: IO () > > > main > > > = start hello > > > > > > hello :: IO () > > > hello > > > = do f <- frame [text := "Hello!"] > > > quit <- button f [text := "Quit", on command := close f] > > > set f [layout := widget quit] > > > > > > with wxhaskell 0.11.0 (latest darcs version), ghc 6.8.3, libwxgtk > > > 2.8.7.1-0ubuntu3 on Kubuntu 8.04 and everything builds fine, but when I > > > try to run it I get: > > > > > > ./wxhaskelltest: symbol lookup error: > > > /usr/lib/libwxc-gtk2.8.7-0.11.0.so: undefined symbol: > > > _ZNK7wxPanel14GetDefaultItemEv > > > > > > Trying > > > > > > strings /usr/lib/libwxc-gtk2.8.7-0.11.0.so | grep wxPanel14 > > > > > > gives: > > > > > > _ZNK7wxPanel14GetDefaultItemEv > > > > > > So the library should be in order. > > > > > > Any help with this? > > > > > > Kind regards, > > > Jeroen Janssen. > > > > > > On Sunday 04 January 2009 16:19:19 Jeremy O'Donoghue wrote: > > > > The wxHaskell development team is pleased to announce the release of > > > > wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. > > > > > > > > The Haskell support is built on a reasonably complete C language > > > > binding, which could be used as the basis for wxWidgets support on > > > > other languages/platforms which do not have easy mechanisms for > > > > linking with C++ code. > > > > > > > > The main highlights of wxHaskell 0.11.1 are: > > > > > > > > - Support for XRC resource files, allowing GUI design using a visual > > > > tool. Note that this > > > > is currently not type safe, and programs will crash if a widget is > > > > not cast to the correct > > > > type on loading. > > > > - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now > > > > dropped and wxHaskell > > > > will not compile against versions of wxWidgets prior to 2.6. This > > > > means that exploratory > > > > development using GHCi is no longer possible. Workaround is to > > > > continue to use older > > > > wxHaskell versions. > > > > - Support for GHC 6.10 > > > > - Preliminary support for Cabal / Hackage > > > > > > > > The full list of changes is provided at the end of this mail. > > > > > > > > Binary packages are available from the wxHaskell download site at > > > > http://sourceforge.net/project/showfiles.php?group_id=73133, for the > > > > following platforms: > > > > > > > > - Windows > > > > - OS X (Intel platform only) > > > > - Source code .tar.gz and .zip > > > > - Documentation (cross-platform) > > > > > > > > The wxHaskell libraries (wxcore and wx) are also available from > > > > Hackage (http://hackage.haskell.org). > > > > > > > > About wxHaskell > > > > --------------- > > > > > > > > wxHaskell is a Haskell binding to the wxWidgets GUI library for > > > > recent versions > > > > of the Glasgow Haskell Compiler. It provides a native look and feel > > > > on Windows, > > > > OS X and Linux, and a medium level programming interface. > > > > > > > > The main project page for wxHaskell is at > > > > http://wxhaskell.sourceforge.net. > > > > The latest source code for wxHaskell can always be obtained from > > > > http://darcs.haskell.org/wxhaskell. > > > > There are developer (wxh...@li... and user > > > > (wxh...@li...) mailing lists, and a wiki > > > > page at http://haskell.org/haskellwiki/WxHaskell which can provide > > > > more information to those interested. > > > > > > > > The C language binding for wxHaskell was derived from an original C > > > > language binding created for the Eiffel programming language by the > > > > ELJ project (http://elj.sourceforge.net). > > > > > > > > Non backward compatible changes: > > > > - Preliminary Cabal / Hackage support > > > > - Added "--global" argument to configure script > > > > - Added "--user" argument to configure script > > > > - Changed wxhaskell official web page to Haskell wiki at > > > > http://haskell.org/haskellwiki/WxHaskell > > > > - Changed official darcs repository to code.haskell.org > > > > - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 > > > > - Adapted some part of wxcore API to be able to refer to wxWidgets > > > > 2.8 documentation for wxcore functions > > > > - Added "TopLevelWindow", which mainly removes some functionality > > > > from "Frame" > > > > - Changed "--with-stc" argument to "--with-contrib" > > > > - Removed "Wave" type synonym > > > > > > > > Backward compatible additions: > > > > - Added support for using XRC resource files to load most controls > > > > and menus attached to frames. > > > > - Added sample file showing how to use XRC support to attach command > > > > handlers to menu items > > > > - Added sample file showing how to use properties with many controls. > > > > - Added "--enable-optimization" argument to configure script > > > > - Added "--O*" argument to configure script > > > > - Added "--enable-library-profiling" argument to configure script > > > > - Added "--p" argument to configure script > > > > - Added "-fvia-C" argument to configure script. And moved this > > > > compilation flag to configure script > > > > - Added Image / ByteString conversion functions > > > > - Adapted the configuration to work with GHC 6.10. > > > > - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread > > > > safety > > > > - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be > > > > more flexible. > > > > - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. > > > > - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use > > > > "wxcMilliSleep" instead > > > > - Added very experimental wxGraphicsContext support > > > > - Added wxSVGFileDC functions > > > > > > > > Bugfixes: > > > > - Applied DEPRECATED pragma to old deprecated functions. Just > > > > documented in Haddock before. > > > > - Fixed "processExecAsync" hangs Windows GUI-only program > > > > - Fixed Windows binary install problem when path with spaces (bug > > > > 1400488) > > > > - Probably fixed the applicattion failed to initialize properly when > > > > using Windows binary. > > > > > > > > -- > > > > Jeremy O'Donoghue > > > > jer...@gm... > > > > > > ----------------------------------------------------------------------- > > >---- --- Check out the new SourceForge.net Marketplace. > > > It is the best place to buy or sell services for > > > just about anything Open Source. > > > http://p.sf.net/sfu/Xq1LFB > > > _______________________________________________ > > > wxhaskell-users mailing list > > > wxh...@li... > > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > > > ------------------------------------------------------------------------- > >----- Check out the new SourceForge.net Marketplace. > > It is the best place to buy or sell services for > > just about anything Open Source. > > http://p.sf.net/sfu/Xq1LFB > > _______________________________________________ > > wxhaskell-users mailing list > > wxh...@li... > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > --------------------------------------------------------------------------- >--- This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Mads L. <mad...@ya...> - 2009-01-14 22:28:52
|
Hi Kellen J. McClain: Which version of libgtk are you running? /Mads > I'm running Fedora 10, and installed wxGTK with "yum", (version > 2.8.9), and have successfully compiled wxhaskell-0.11.0 (using > --with-opengl --with-contrib --with-mediactrl --wx-toolkit=gtk2), but > whenever I run any of the sample programs, no windows pop up, and the > same error occurs: > > (process:16395): GLib-GObject-CRITICAL **: gtype.c:2458: > initialization assertion failed, use IA__g_type_init() prior to this > function > > (process:16395): GLib-CRITICAL **: g_once_init_leave: assertion > `initialization_value != 0' failed > > (process:16395): Gdk-CRITICAL **: gdk_cursor_new_for_display: > assertion `GDK_IS_DISPLAY (display)' failed > > I tried running a sample program written in C++ and it ran fine, so > I'm thinking that it is a problem with something in wxhaskell. I > noticed that Jose Ramirez in 2008-08-12 came across the same problem > (http://sourceforge.net/mailarchive/message.php?msg_name=89c11d70808120559j63465383r1c61f4c11a46d47c%40mail.gmail.com). Did anyone figure out what the problem was? > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ wxhaskell-users mailing list wxh...@li... https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Mads L. <mad...@ya...> - 2009-01-14 22:28:17
|
Hi Jeroen Janssen: Which version of libgtk are you running? /Mads > Follow-up: > > With latest darcs version, showing revision 0.11.1 this time, this error does > not occur any longer. However, wxhaskell is still not working as now > programs fail with: > > (process:3353): GLib-GObject-CRITICAL > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > assertion failed, use IA__g_type_init() prior to this function > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > `initialization_value != 0' failed > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > `GDK_IS_DISPLAY (display)' failed > > This happens for the example I mentioned in my previous e-mail but also for > the examples included with wxhaskell (BoxedCombinator etc). > > Any help with this? The parameters stayed the same as in my previous e-mail > (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even tried updating to > wxwidgets 2.8.9, but to no avail, same error. > I build wxhaskell with "cabal" install, followed by the cd wx en usual build > process if that may be of any help. > > Kind regards, > > > On Tuesday 06 January 2009 19:27:32 Jeroen Janssen wrote: > > Hi, > > > > I tried compiling this program: > > > > module Main where > > > > import Graphics.UI.WX > > > > main :: IO () > > main > > = start hello > > > > hello :: IO () > > hello > > = do f <- frame [text := "Hello!"] > > quit <- button f [text := "Quit", on command := close f] > > set f [layout := widget quit] > > > > with wxhaskell 0.11.0 (latest darcs version), ghc 6.8.3, libwxgtk > > 2.8.7.1-0ubuntu3 on Kubuntu 8.04 and everything builds fine, but when I try > > to run it I get: > > > > ./wxhaskelltest: symbol lookup error: /usr/lib/libwxc-gtk2.8.7-0.11.0.so: > > undefined symbol: _ZNK7wxPanel14GetDefaultItemEv > > > > Trying > > > > strings /usr/lib/libwxc-gtk2.8.7-0.11.0.so | grep wxPanel14 > > > > gives: > > > > _ZNK7wxPanel14GetDefaultItemEv > > > > So the library should be in order. > > > > Any help with this? > > > > Kind regards, > > Jeroen Janssen. > > > > On Sunday 04 January 2009 16:19:19 Jeremy O'Donoghue wrote: > > > The wxHaskell development team is pleased to announce the release of > > > wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. > > > > > > The Haskell support is built on a reasonably complete C language > > > binding, which could be used as the basis for wxWidgets support on other > > > languages/platforms which do not have easy mechanisms for linking with > > > C++ code. > > > > > > The main highlights of wxHaskell 0.11.1 are: > > > > > > - Support for XRC resource files, allowing GUI design using a visual > > > tool. Note that this > > > is currently not type safe, and programs will crash if a widget is > > > not cast to the correct > > > type on loading. > > > - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now > > > dropped and wxHaskell > > > will not compile against versions of wxWidgets prior to 2.6. This > > > means that exploratory > > > development using GHCi is no longer possible. Workaround is to > > > continue to use older > > > wxHaskell versions. > > > - Support for GHC 6.10 > > > - Preliminary support for Cabal / Hackage > > > > > > The full list of changes is provided at the end of this mail. > > > > > > Binary packages are available from the wxHaskell download site at > > > http://sourceforge.net/project/showfiles.php?group_id=73133, for the > > > following platforms: > > > > > > - Windows > > > - OS X (Intel platform only) > > > - Source code .tar.gz and .zip > > > - Documentation (cross-platform) > > > > > > The wxHaskell libraries (wxcore and wx) are also available from Hackage > > > (http://hackage.haskell.org). > > > > > > About wxHaskell > > > --------------- > > > > > > wxHaskell is a Haskell binding to the wxWidgets GUI library for recent > > > versions > > > of the Glasgow Haskell Compiler. It provides a native look and feel on > > > Windows, > > > OS X and Linux, and a medium level programming interface. > > > > > > The main project page for wxHaskell is at > > > http://wxhaskell.sourceforge.net. > > > The latest source code for wxHaskell can always be obtained from > > > http://darcs.haskell.org/wxhaskell. > > > There are developer (wxh...@li... and user > > > (wxh...@li...) mailing lists, and a wiki page > > > at http://haskell.org/haskellwiki/WxHaskell which can provide more > > > information to those interested. > > > > > > The C language binding for wxHaskell was derived from an original C > > > language binding created for the Eiffel programming language by the > > > ELJ project (http://elj.sourceforge.net). > > > > > > Non backward compatible changes: > > > - Preliminary Cabal / Hackage support > > > - Added "--global" argument to configure script > > > - Added "--user" argument to configure script > > > - Changed wxhaskell official web page to Haskell wiki at > > > http://haskell.org/haskellwiki/WxHaskell > > > - Changed official darcs repository to code.haskell.org > > > - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 > > > - Adapted some part of wxcore API to be able to refer to wxWidgets 2.8 > > > documentation for wxcore functions > > > - Added "TopLevelWindow", which mainly removes some functionality from > > > "Frame" > > > - Changed "--with-stc" argument to "--with-contrib" > > > - Removed "Wave" type synonym > > > > > > Backward compatible additions: > > > - Added support for using XRC resource files to load most controls and > > > menus attached to frames. > > > - Added sample file showing how to use XRC support to attach command > > > handlers to menu items > > > - Added sample file showing how to use properties with many controls. > > > - Added "--enable-optimization" argument to configure script > > > - Added "--O*" argument to configure script > > > - Added "--enable-library-profiling" argument to configure script > > > - Added "--p" argument to configure script > > > - Added "-fvia-C" argument to configure script. And moved this > > > compilation flag to configure script > > > - Added Image / ByteString conversion functions > > > - Adapted the configuration to work with GHC 6.10. > > > - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread > > > safety > > > - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be > > > more flexible. > > > - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. > > > - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use > > > "wxcMilliSleep" instead > > > - Added very experimental wxGraphicsContext support > > > - Added wxSVGFileDC functions > > > > > > Bugfixes: > > > - Applied DEPRECATED pragma to old deprecated functions. Just documented > > > in Haddock before. > > > - Fixed "processExecAsync" hangs Windows GUI-only program > > > - Fixed Windows binary install problem when path with spaces (bug > > > 1400488) > > > - Probably fixed the applicattion failed to initialize properly when > > > using Windows binary. > > > > > > -- > > > Jeremy O'Donoghue > > > jer...@gm... > > > > --------------------------------------------------------------------------- > >--- Check out the new SourceForge.net Marketplace. > > It is the best place to buy or sell services for > > just about anything Open Source. > > http://p.sf.net/sfu/Xq1LFB > > _______________________________________________ > > wxhaskell-users mailing list > > wxh...@li... > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Jeroen J. <Jer...@vu...> - 2009-01-12 09:57:24
|
Follow-up: the same problems persist with ghc 6.10.1. On Monday 12 January 2009 09:30:58 Jeroen Janssen wrote: > Hey Mads, > > This seems to be correct. If I modify my testprogram to this: > > module Main where > > import Graphics.UI.WX > import System.IO > > main :: IO () > main > = do hPutStrLn stderr "WX checkpoint alpha" > --start hello > > hello :: IO () > hello > = do f <- frame [text := "Hello!"] > quit <- button f [text := "Quit", on command := close f] > set f [layout := widget quit] > > Where start does not even get called, I get the same errors and infinite > loop (without ever getting the "WX checkpoint alpha"). Removing the hello > function and the import function outputs the string correctly without any > errors. > > The strangest thing is that wxpython works flawlessly, so I am not sure > whether the problem is not in part due to some bug with ghc 6.8.3. > > On Monday 12 January 2009 00:33:05 Mads Lindstrøm wrote: > > Hi Jeroen > > > > I wrote: > > > Hi Jeroen > > > > > > While my windows show up just fine, I do get similar warnings to you: > > > > > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > > assertion failed, use IA__g_type_init() prior to this function > > > > > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > > `GDK_IS_DISPLAY (display)' failed > > > > > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > > assertion failed, use IA__g_type_init() prior to this function > > > > > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > > `GDK_IS_DISPLAY (display)' failed > > > > > > I think we to call g_type_init() > > > (http://library.gnome.org/devel/gobject/unstable/gobject-Type-Informati > > >on .html#g-type-init) somewhere in the wxHaskell code, to avoid these > > > warnings and possibly your wxHaskell to work. I am looking into it. > > > > I changed the start-function (in wx/src/Graphics/UI/WX.hs) from: > > > > -- | 'start' runs the GUI. > > start :: IO a -> IO () > > start io > > = run (unitIO io) > > > > to: > > > > -- | 'start' runs the GUI. > > start :: IO a -> IO () > > start io > > = do hPutStrLn stderr "WX checkpoint alpha" > > hFlush stderr > > run (unitIO io) > > > > And I now get the output: > > > > (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed > > > > (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed WX checkpoint alpha > > > > > > That is, the checkpoint comes _after_ the GLib error, and as the > > start-function is the very first function to be called, it leads me to > > conclude that the error is not with the Haskell code. So I assume it > > must be some library initialization. Unfortunately, I have no knowledge > > of whats gets called as part of library initialization and I do not know > > where to look. If anyway, can help me with this I would be most happy. > > > > > > Greetings > > > > Mads Lindstrøm > > > > > This bugs seems to be similar to what you (and I) are experiencing > > > https://bugzilla.redhat.com/show_bug.cgi?id=442977 . > > > > > > > > > Greetings, > > > > > > Mads Lindstrøm > > > > > > Jeroen Janssen wrote: > > > > Follow-up: > > > > > > > > With latest darcs version, showing revision 0.11.1 this time, this > > > > error does not occur any longer. However, wxhaskell is still not > > > > working as now programs fail with: > > > > > > > > (process:3353): GLib-GObject-CRITICAL > > > > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > > > > assertion failed, use IA__g_type_init() prior to this function > > > > > > > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > > > > `initialization_value != 0' failed > > > > > > > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: > > > > assertion `GDK_IS_DISPLAY (display)' failed > > > > > > > > This happens for the example I mentioned in my previous e-mail but > > > > also for the examples included with wxhaskell (BoxedCombinator etc). > > > > > > > > Any help with this? The parameters stayed the same as in my previous > > > > e-mail (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even > > > > tried updating to wxwidgets 2.8.9, but to no avail, same error. > > > > I build wxhaskell with "cabal" install, followed by the cd wx en > > > > usual build process if that may be of any help. > > > > > > > > Kind regards, > > > > ------------------------------------------------------------------------- > >-- --- Check out the new SourceForge.net Marketplace. > > It is the best place to buy or sell services for > > just about anything Open Source. > > http://p.sf.net/sfu/Xq1LFB > > _______________________________________________ > > wxhaskell-users mailing list > > wxh...@li... > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > --------------------------------------------------------------------------- >--- Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Jeroen J. <Jer...@ug...> - 2009-01-12 08:33:30
|
Hey Mads, This seems to be correct. If I modify my testprogram to this: module Main where import Graphics.UI.WX import System.IO main :: IO () main = do hPutStrLn stderr "WX checkpoint alpha" --start hello hello :: IO () hello = do f <- frame [text := "Hello!"] quit <- button f [text := "Quit", on command := close f] set f [layout := widget quit] Where start does not even get called, I get the same errors and infinite loop (without ever getting the "WX checkpoint alpha"). Removing the hello function and the import function outputs the string correctly without any errors. The strangest thing is that wxpython works flawlessly, so I am not sure whether the problem is not in part due to some bug with ghc 6.8.3. On Monday 12 January 2009 00:33:05 Mads Lindstrøm wrote: > Hi Jeroen > > I wrote: > > Hi Jeroen > > > > While my windows show up just fine, I do get similar warnings to you: > > > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed > > > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed > > > > I think we to call g_type_init() > > (http://library.gnome.org/devel/gobject/unstable/gobject-Type-Information > >.html#g-type-init) somewhere in the wxHaskell code, to avoid these > > warnings and possibly your wxHaskell to work. I am looking into it. > > I changed the start-function (in wx/src/Graphics/UI/WX.hs) from: > > -- | 'start' runs the GUI. > start :: IO a -> IO () > start io > = run (unitIO io) > > to: > > -- | 'start' runs the GUI. > start :: IO a -> IO () > start io > = do hPutStrLn stderr "WX checkpoint alpha" > hFlush stderr > run (unitIO io) > > And I now get the output: > > (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > assertion failed, use IA__g_type_init() prior to this function > > (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > `GDK_IS_DISPLAY (display)' failed > > (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization > assertion failed, use IA__g_type_init() prior to this function > > (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > `GDK_IS_DISPLAY (display)' failed WX checkpoint alpha > > > That is, the checkpoint comes _after_ the GLib error, and as the > start-function is the very first function to be called, it leads me to > conclude that the error is not with the Haskell code. So I assume it > must be some library initialization. Unfortunately, I have no knowledge > of whats gets called as part of library initialization and I do not know > where to look. If anyway, can help me with this I would be most happy. > > > Greetings > > Mads Lindstrøm > > > This bugs seems to be similar to what you (and I) are experiencing > > https://bugzilla.redhat.com/show_bug.cgi?id=442977 . > > > > > > Greetings, > > > > Mads Lindstrøm > > > > Jeroen Janssen wrote: > > > Follow-up: > > > > > > With latest darcs version, showing revision 0.11.1 this time, this > > > error does not occur any longer. However, wxhaskell is still not > > > working as now programs fail with: > > > > > > (process:3353): GLib-GObject-CRITICAL > > > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > > > assertion failed, use IA__g_type_init() prior to this function > > > > > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > > > `initialization_value != 0' failed > > > > > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > > `GDK_IS_DISPLAY (display)' failed > > > > > > This happens for the example I mentioned in my previous e-mail but also > > > for the examples included with wxhaskell (BoxedCombinator etc). > > > > > > Any help with this? The parameters stayed the same as in my previous > > > e-mail (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even > > > tried updating to wxwidgets 2.8.9, but to no avail, same error. > > > I build wxhaskell with "cabal" install, followed by the cd wx en usual > > > build process if that may be of any help. > > > > > > Kind regards, > > --------------------------------------------------------------------------- >--- Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Mads L. <mad...@ya...> - 2009-01-11 23:37:42
|
Hi Jeroen I wrote: > Hi Jeroen > > While my windows show up just fine, I do get similar warnings to you: > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed > > (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function > > (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed > > I think we to call g_type_init() > (http://library.gnome.org/devel/gobject/unstable/gobject-Type-Information.html#g-type-init) somewhere in the wxHaskell code, to avoid these warnings and possibly your wxHaskell to work. I am looking into it. I changed the start-function (in wx/src/Graphics/UI/WX.hs) from: -- | 'start' runs the GUI. start :: IO a -> IO () start io = run (unitIO io) to: -- | 'start' runs the GUI. start :: IO a -> IO () start io = do hPutStrLn stderr "WX checkpoint alpha" hFlush stderr run (unitIO io) And I now get the output: (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed (process:14665): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function (process:14665): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed WX checkpoint alpha That is, the checkpoint comes _after_ the GLib error, and as the start-function is the very first function to be called, it leads me to conclude that the error is not with the Haskell code. So I assume it must be some library initialization. Unfortunately, I have no knowledge of whats gets called as part of library initialization and I do not know where to look. If anyway, can help me with this I would be most happy. Greetings Mads Lindstrøm > > This bugs seems to be similar to what you (and I) are experiencing > https://bugzilla.redhat.com/show_bug.cgi?id=442977 . > > > Greetings, > > Mads Lindstrøm > > Jeroen Janssen wrote: > > Follow-up: > > > > With latest darcs version, showing revision 0.11.1 this time, this error does > > not occur any longer. However, wxhaskell is still not working as now > > programs fail with: > > > > (process:3353): GLib-GObject-CRITICAL > > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > > assertion failed, use IA__g_type_init() prior to this function > > > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > > `initialization_value != 0' failed > > > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > > `GDK_IS_DISPLAY (display)' failed > > > > This happens for the example I mentioned in my previous e-mail but also for > > the examples included with wxhaskell (BoxedCombinator etc). > > > > Any help with this? The parameters stayed the same as in my previous e-mail > > (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even tried updating to > > wxwidgets 2.8.9, but to no avail, same error. > > I build wxhaskell with "cabal" install, followed by the cd wx en usual build > > process if that may be of any help. > > > > Kind regards, > > > > |
From: Mads L. <mad...@ya...> - 2009-01-11 16:22:33
|
Hi Jeroen While my windows show up just fine, I do get similar warnings to you: (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed (process:12227): GLib-GObject-CRITICAL **: gtype.c:2240: initialization assertion failed, use IA__g_type_init() prior to this function (process:12227): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed I think we to call g_type_init() (http://library.gnome.org/devel/gobject/unstable/gobject-Type-Information.html#g-type-init) somewhere in the wxHaskell code, to avoid these warnings and possibly your wxHaskell to work. I am looking into it. This bugs seems to be similar to what you (and I) are experiencing https://bugzilla.redhat.com/show_bug.cgi?id=442977 . Greetings, Mads Lindstrøm Jeroen Janssen wrote: > Follow-up: > > With latest darcs version, showing revision 0.11.1 this time, this error does > not occur any longer. However, wxhaskell is still not working as now > programs fail with: > > (process:3353): GLib-GObject-CRITICAL > **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization > assertion failed, use IA__g_type_init() prior to this function > > (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion > `initialization_value != 0' failed > > (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > `GDK_IS_DISPLAY (display)' failed > > This happens for the example I mentioned in my previous e-mail but also for > the examples included with wxhaskell (BoxedCombinator etc). > > Any help with this? The parameters stayed the same as in my previous e-mail > (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even tried updating to > wxwidgets 2.8.9, but to no avail, same error. > I build wxhaskell with "cabal" install, followed by the cd wx en usual build > process if that may be of any help. > > Kind regards, > > > On Tuesday 06 January 2009 19:27:32 Jeroen Janssen wrote: > > Hi, > > > > I tried compiling this program: > > > > module Main where > > > > import Graphics.UI.WX > > > > main :: IO () > > main > > = start hello > > > > hello :: IO () > > hello > > = do f <- frame [text := "Hello!"] > > quit <- button f [text := "Quit", on command := close f] > > set f [layout := widget quit] > > > > with wxhaskell 0.11.0 (latest darcs version), ghc 6.8.3, libwxgtk > > 2.8.7.1-0ubuntu3 on Kubuntu 8.04 and everything builds fine, but when I try > > to run it I get: > > > > ./wxhaskelltest: symbol lookup error: /usr/lib/libwxc-gtk2.8.7-0.11.0.so: > > undefined symbol: _ZNK7wxPanel14GetDefaultItemEv > > > > Trying > > > > strings /usr/lib/libwxc-gtk2.8.7-0.11.0.so | grep wxPanel14 > > > > gives: > > > > _ZNK7wxPanel14GetDefaultItemEv > > > > So the library should be in order. > > > > Any help with this? > > > > Kind regards, > > Jeroen Janssen. > > > > On Sunday 04 January 2009 16:19:19 Jeremy O'Donoghue wrote: > > > The wxHaskell development team is pleased to announce the release of > > > wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. > > > > > > The Haskell support is built on a reasonably complete C language > > > binding, which could be used as the basis for wxWidgets support on other > > > languages/platforms which do not have easy mechanisms for linking with > > > C++ code. > > > > > > The main highlights of wxHaskell 0.11.1 are: > > > > > > - Support for XRC resource files, allowing GUI design using a visual > > > tool. Note that this > > > is currently not type safe, and programs will crash if a widget is > > > not cast to the correct > > > type on loading. > > > - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now > > > dropped and wxHaskell > > > will not compile against versions of wxWidgets prior to 2.6. This > > > means that exploratory > > > development using GHCi is no longer possible. Workaround is to > > > continue to use older > > > wxHaskell versions. > > > - Support for GHC 6.10 > > > - Preliminary support for Cabal / Hackage > > > > > > The full list of changes is provided at the end of this mail. > > > > > > Binary packages are available from the wxHaskell download site at > > > http://sourceforge.net/project/showfiles.php?group_id=73133, for the > > > following platforms: > > > > > > - Windows > > > - OS X (Intel platform only) > > > - Source code .tar.gz and .zip > > > - Documentation (cross-platform) > > > > > > The wxHaskell libraries (wxcore and wx) are also available from Hackage > > > (http://hackage.haskell.org). > > > > > > About wxHaskell > > > --------------- > > > > > > wxHaskell is a Haskell binding to the wxWidgets GUI library for recent > > > versions > > > of the Glasgow Haskell Compiler. It provides a native look and feel on > > > Windows, > > > OS X and Linux, and a medium level programming interface. > > > > > > The main project page for wxHaskell is at > > > http://wxhaskell.sourceforge.net. > > > The latest source code for wxHaskell can always be obtained from > > > http://darcs.haskell.org/wxhaskell. > > > There are developer (wxh...@li... and user > > > (wxh...@li...) mailing lists, and a wiki page > > > at http://haskell.org/haskellwiki/WxHaskell which can provide more > > > information to those interested. > > > > > > The C language binding for wxHaskell was derived from an original C > > > language binding created for the Eiffel programming language by the > > > ELJ project (http://elj.sourceforge.net). > > > > > > Non backward compatible changes: > > > - Preliminary Cabal / Hackage support > > > - Added "--global" argument to configure script > > > - Added "--user" argument to configure script > > > - Changed wxhaskell official web page to Haskell wiki at > > > http://haskell.org/haskellwiki/WxHaskell > > > - Changed official darcs repository to code.haskell.org > > > - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 > > > - Adapted some part of wxcore API to be able to refer to wxWidgets 2.8 > > > documentation for wxcore functions > > > - Added "TopLevelWindow", which mainly removes some functionality from > > > "Frame" > > > - Changed "--with-stc" argument to "--with-contrib" > > > - Removed "Wave" type synonym > > > > > > Backward compatible additions: > > > - Added support for using XRC resource files to load most controls and > > > menus attached to frames. > > > - Added sample file showing how to use XRC support to attach command > > > handlers to menu items > > > - Added sample file showing how to use properties with many controls. > > > - Added "--enable-optimization" argument to configure script > > > - Added "--O*" argument to configure script > > > - Added "--enable-library-profiling" argument to configure script > > > - Added "--p" argument to configure script > > > - Added "-fvia-C" argument to configure script. And moved this > > > compilation flag to configure script > > > - Added Image / ByteString conversion functions > > > - Adapted the configuration to work with GHC 6.10. > > > - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread > > > safety > > > - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be > > > more flexible. > > > - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. > > > - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use > > > "wxcMilliSleep" instead > > > - Added very experimental wxGraphicsContext support > > > - Added wxSVGFileDC functions > > > > > > Bugfixes: > > > - Applied DEPRECATED pragma to old deprecated functions. Just documented > > > in Haddock before. > > > - Fixed "processExecAsync" hangs Windows GUI-only program > > > - Fixed Windows binary install problem when path with spaces (bug > > > 1400488) > > > - Probably fixed the applicattion failed to initialize properly when > > > using Windows binary. > > > > > > -- > > > Jeremy O'Donoghue > > > jer...@gm... > > > > --------------------------------------------------------------------------- > >--- Check out the new SourceForge.net Marketplace. > > It is the best place to buy or sell services for > > just about anything Open Source. > > http://p.sf.net/sfu/Xq1LFB > > _______________________________________________ > > wxhaskell-users mailing list > > wxh...@li... > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Jeroen J. <Jer...@ug...> - 2009-01-11 12:34:40
|
I am having the same problem (see my earlier e-mails on the list) on Ubuntu with both wxGTK 2.8.9 and 2.8.7. Unfortunately noone has replied to my previous e-mail yet. On Saturday 10 January 2009 21:53:14 Kellen J. McClain wrote: > I'm running Fedora 10, and installed wxGTK with "yum", (version 2.8.9), > and have successfully compiled wxhaskell-0.11.0 (using --with-opengl > --with-contrib --with-mediactrl --wx-toolkit=gtk2), but whenever I run > any of the sample programs, no windows pop up, and the same error > occurs: > > (process:16395): GLib-GObject-CRITICAL **: gtype.c:2458: initialization > assertion failed, use IA__g_type_init() prior to this function > > (process:16395): GLib-CRITICAL **: g_once_init_leave: assertion > `initialization_value != 0' failed > > (process:16395): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion > `GDK_IS_DISPLAY (display)' failed > > I tried running a sample program written in C++ and it ran fine, so I'm > thinking that it is a problem with something in wxhaskell. I noticed > that Jose Ramirez in 2008-08-12 came across the same problem > (http://sourceforge.net/mailarchive/message.php?msg_name=89c11d70808120559j >63465383r1c61f4c11a46d47c%40mail.gmail.com). Did anyone figure out what the > problem was? |
From: Henk-Jan v. T. <hj...@ch...> - 2009-01-10 22:57:04
|
L.S., I created a bitmapButton as follows: > ok <- bitmapButton f [ on command := close f, picture := > "button62.gif", text := "Ok" ] The picture is not shown in full; how can I get this correct? I found out that wxPython has wx.BU_EXACTFIT to make the button exactly the size of the image; is there anything like that in wxHaskell? -- Regards, Henk-Jan van Tuyl -- http://functor.bamikanarie.com http://Van.Tuyl.eu/ -- |
From: Kellen J. M. <kjm...@co...> - 2009-01-10 20:53:22
|
I'm running Fedora 10, and installed wxGTK with "yum", (version 2.8.9), and have successfully compiled wxhaskell-0.11.0 (using --with-opengl --with-contrib --with-mediactrl --wx-toolkit=gtk2), but whenever I run any of the sample programs, no windows pop up, and the same error occurs: (process:16395): GLib-GObject-CRITICAL **: gtype.c:2458: initialization assertion failed, use IA__g_type_init() prior to this function (process:16395): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (process:16395): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed I tried running a sample program written in C++ and it ran fine, so I'm thinking that it is a problem with something in wxhaskell. I noticed that Jose Ramirez in 2008-08-12 came across the same problem (http://sourceforge.net/mailarchive/message.php?msg_name=89c11d70808120559j63465383r1c61f4c11a46d47c%40mail.gmail.com). Did anyone figure out what the problem was? |
From: Jeroen J. <Jer...@ug...> - 2009-01-07 19:44:56
|
Follow-up: With latest darcs version, showing revision 0.11.1 this time, this error does not occur any longer. However, wxhaskell is still not working as now programs fail with: (process:3353): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.16.6/gobject/gtype.c:2248: initialization assertion failed, use IA__g_type_init() prior to this function (process:3353): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (process:3353): Gdk-CRITICAL **: gdk_cursor_new_for_display: assertion `GDK_IS_DISPLAY (display)' failed This happens for the example I mentioned in my previous e-mail but also for the examples included with wxhaskell (BoxedCombinator etc). Any help with this? The parameters stayed the same as in my previous e-mail (Ubuntu 8.04, wxwidgets/wxgtk 2.8.7 ubuntu version), I even tried updating to wxwidgets 2.8.9, but to no avail, same error. I build wxhaskell with "cabal" install, followed by the cd wx en usual build process if that may be of any help. Kind regards, On Tuesday 06 January 2009 19:27:32 Jeroen Janssen wrote: > Hi, > > I tried compiling this program: > > module Main where > > import Graphics.UI.WX > > main :: IO () > main > = start hello > > hello :: IO () > hello > = do f <- frame [text := "Hello!"] > quit <- button f [text := "Quit", on command := close f] > set f [layout := widget quit] > > with wxhaskell 0.11.0 (latest darcs version), ghc 6.8.3, libwxgtk > 2.8.7.1-0ubuntu3 on Kubuntu 8.04 and everything builds fine, but when I try > to run it I get: > > ./wxhaskelltest: symbol lookup error: /usr/lib/libwxc-gtk2.8.7-0.11.0.so: > undefined symbol: _ZNK7wxPanel14GetDefaultItemEv > > Trying > > strings /usr/lib/libwxc-gtk2.8.7-0.11.0.so | grep wxPanel14 > > gives: > > _ZNK7wxPanel14GetDefaultItemEv > > So the library should be in order. > > Any help with this? > > Kind regards, > Jeroen Janssen. > > On Sunday 04 January 2009 16:19:19 Jeremy O'Donoghue wrote: > > The wxHaskell development team is pleased to announce the release of > > wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. > > > > The Haskell support is built on a reasonably complete C language > > binding, which could be used as the basis for wxWidgets support on other > > languages/platforms which do not have easy mechanisms for linking with > > C++ code. > > > > The main highlights of wxHaskell 0.11.1 are: > > > > - Support for XRC resource files, allowing GUI design using a visual > > tool. Note that this > > is currently not type safe, and programs will crash if a widget is > > not cast to the correct > > type on loading. > > - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now > > dropped and wxHaskell > > will not compile against versions of wxWidgets prior to 2.6. This > > means that exploratory > > development using GHCi is no longer possible. Workaround is to > > continue to use older > > wxHaskell versions. > > - Support for GHC 6.10 > > - Preliminary support for Cabal / Hackage > > > > The full list of changes is provided at the end of this mail. > > > > Binary packages are available from the wxHaskell download site at > > http://sourceforge.net/project/showfiles.php?group_id=73133, for the > > following platforms: > > > > - Windows > > - OS X (Intel platform only) > > - Source code .tar.gz and .zip > > - Documentation (cross-platform) > > > > The wxHaskell libraries (wxcore and wx) are also available from Hackage > > (http://hackage.haskell.org). > > > > About wxHaskell > > --------------- > > > > wxHaskell is a Haskell binding to the wxWidgets GUI library for recent > > versions > > of the Glasgow Haskell Compiler. It provides a native look and feel on > > Windows, > > OS X and Linux, and a medium level programming interface. > > > > The main project page for wxHaskell is at > > http://wxhaskell.sourceforge.net. > > The latest source code for wxHaskell can always be obtained from > > http://darcs.haskell.org/wxhaskell. > > There are developer (wxh...@li... and user > > (wxh...@li...) mailing lists, and a wiki page > > at http://haskell.org/haskellwiki/WxHaskell which can provide more > > information to those interested. > > > > The C language binding for wxHaskell was derived from an original C > > language binding created for the Eiffel programming language by the > > ELJ project (http://elj.sourceforge.net). > > > > Non backward compatible changes: > > - Preliminary Cabal / Hackage support > > - Added "--global" argument to configure script > > - Added "--user" argument to configure script > > - Changed wxhaskell official web page to Haskell wiki at > > http://haskell.org/haskellwiki/WxHaskell > > - Changed official darcs repository to code.haskell.org > > - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 > > - Adapted some part of wxcore API to be able to refer to wxWidgets 2.8 > > documentation for wxcore functions > > - Added "TopLevelWindow", which mainly removes some functionality from > > "Frame" > > - Changed "--with-stc" argument to "--with-contrib" > > - Removed "Wave" type synonym > > > > Backward compatible additions: > > - Added support for using XRC resource files to load most controls and > > menus attached to frames. > > - Added sample file showing how to use XRC support to attach command > > handlers to menu items > > - Added sample file showing how to use properties with many controls. > > - Added "--enable-optimization" argument to configure script > > - Added "--O*" argument to configure script > > - Added "--enable-library-profiling" argument to configure script > > - Added "--p" argument to configure script > > - Added "-fvia-C" argument to configure script. And moved this > > compilation flag to configure script > > - Added Image / ByteString conversion functions > > - Adapted the configuration to work with GHC 6.10. > > - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread > > safety > > - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be > > more flexible. > > - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. > > - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use > > "wxcMilliSleep" instead > > - Added very experimental wxGraphicsContext support > > - Added wxSVGFileDC functions > > > > Bugfixes: > > - Applied DEPRECATED pragma to old deprecated functions. Just documented > > in Haddock before. > > - Fixed "processExecAsync" hangs Windows GUI-only program > > - Fixed Windows binary install problem when path with spaces (bug > > 1400488) > > - Probably fixed the applicattion failed to initialize properly when > > using Windows binary. > > > > -- > > Jeremy O'Donoghue > > jer...@gm... > > --------------------------------------------------------------------------- >--- Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Jeroen J. <Jer...@vu...> - 2009-01-06 18:27:37
|
Hi, I tried compiling this program: module Main where import Graphics.UI.WX main :: IO () main = start hello hello :: IO () hello = do f <- frame [text := "Hello!"] quit <- button f [text := "Quit", on command := close f] set f [layout := widget quit] with wxhaskell 0.11.0 (latest darcs version), ghc 6.8.3, libwxgtk 2.8.7.1-0ubuntu3 on Kubuntu 8.04 and everything builds fine, but when I try to run it I get: ./wxhaskelltest: symbol lookup error: /usr/lib/libwxc-gtk2.8.7-0.11.0.so: undefined symbol: _ZNK7wxPanel14GetDefaultItemEv Trying strings /usr/lib/libwxc-gtk2.8.7-0.11.0.so | grep wxPanel14 gives: _ZNK7wxPanel14GetDefaultItemEv So the library should be in order. Any help with this? Kind regards, Jeroen Janssen. On Sunday 04 January 2009 16:19:19 Jeremy O'Donoghue wrote: > The wxHaskell development team is pleased to announce the release of > wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. > > The Haskell support is built on a reasonably complete C language > binding, which could be used as the basis for wxWidgets support on other > languages/platforms which do not have easy mechanisms for linking with > C++ code. > > The main highlights of wxHaskell 0.11.1 are: > > - Support for XRC resource files, allowing GUI design using a visual > tool. Note that this > is currently not type safe, and programs will crash if a widget is > not cast to the correct > type on loading. > - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now > dropped and wxHaskell > will not compile against versions of wxWidgets prior to 2.6. This > means that exploratory > development using GHCi is no longer possible. Workaround is to > continue to use older > wxHaskell versions. > - Support for GHC 6.10 > - Preliminary support for Cabal / Hackage > > The full list of changes is provided at the end of this mail. > > Binary packages are available from the wxHaskell download site at > http://sourceforge.net/project/showfiles.php?group_id=73133, for the > following platforms: > > - Windows > - OS X (Intel platform only) > - Source code .tar.gz and .zip > - Documentation (cross-platform) > > The wxHaskell libraries (wxcore and wx) are also available from Hackage > (http://hackage.haskell.org). > > About wxHaskell > --------------- > > wxHaskell is a Haskell binding to the wxWidgets GUI library for recent > versions > of the Glasgow Haskell Compiler. It provides a native look and feel on > Windows, > OS X and Linux, and a medium level programming interface. > > The main project page for wxHaskell is at > http://wxhaskell.sourceforge.net. > The latest source code for wxHaskell can always be obtained from > http://darcs.haskell.org/wxhaskell. > There are developer (wxh...@li... and user > (wxh...@li...) mailing lists, and a wiki page > at http://haskell.org/haskellwiki/WxHaskell which can provide more > information to those interested. > > The C language binding for wxHaskell was derived from an original C > language binding created for the Eiffel programming language by the > ELJ project (http://elj.sourceforge.net). > > Non backward compatible changes: > - Preliminary Cabal / Hackage support > - Added "--global" argument to configure script > - Added "--user" argument to configure script > - Changed wxhaskell official web page to Haskell wiki at > http://haskell.org/haskellwiki/WxHaskell > - Changed official darcs repository to code.haskell.org > - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 > - Adapted some part of wxcore API to be able to refer to wxWidgets 2.8 > documentation for wxcore functions > - Added "TopLevelWindow", which mainly removes some functionality from > "Frame" > - Changed "--with-stc" argument to "--with-contrib" > - Removed "Wave" type synonym > > Backward compatible additions: > - Added support for using XRC resource files to load most controls and > menus attached to frames. > - Added sample file showing how to use XRC support to attach command > handlers to menu items > - Added sample file showing how to use properties with many controls. > - Added "--enable-optimization" argument to configure script > - Added "--O*" argument to configure script > - Added "--enable-library-profiling" argument to configure script > - Added "--p" argument to configure script > - Added "-fvia-C" argument to configure script. And moved this > compilation flag to configure script > - Added Image / ByteString conversion functions > - Adapted the configuration to work with GHC 6.10. > - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread > safety > - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be > more flexible. > - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. > - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use > "wxcMilliSleep" instead > - Added very experimental wxGraphicsContext support > - Added wxSVGFileDC functions > > Bugfixes: > - Applied DEPRECATED pragma to old deprecated functions. Just documented > in Haddock before. > - Fixed "processExecAsync" hangs Windows GUI-only program > - Fixed Windows binary install problem when path with spaces (bug > 1400488) > - Probably fixed the applicattion failed to initialize properly when > using Windows binary. > > -- > Jeremy O'Donoghue > jer...@gm... |
From: Bernd H. <ber...@ic...> - 2009-01-06 13:10:55
|
Hi, thanks for adding this function to enable adding bitmaps for tool bar items from a resource file. I'm sorry to note that on my Windows XP the extension does not work. Perhaps you can add this to your bug list!? In detail: In my application, I defined a function to use the new functionality like this: myToolMenu tbar menuItem iconName = do icon <- iconCreateLoad iconName wxBITMAP_TYPE_BMP_RESOURCE (sz 16 16) -- does not display bitmaps! -- icon <- iconCreateLoad iconName wxBITMAP_TYPE_ICO_RESOURCE (sz 16 16) -- crashes! toolMenuFromBitmap tbar menuItem "" icon [] I observe the following behavior: a) When using wxBITMAP_TYPE_BMP_RESOURCE the application starts, but no bitmaps are displayed for the tool items. b) When using wxBITMAP_TYPE_ICO_RESOURCE the application crashes when starting The resource file looks as follows: ABOUT ICON DISCARDABLE "bitmaps/about.ico" CLOSETAB ICON DISCARDABLE "bitmaps/closetab.ico" ... which is compiled to a .o file using windres.exe from ghc-6.10.1\bin and the mingw gcc and then linked to the executable. In contrast, setting the icon for the top level window using this method works fine: ico_about <- iconCreateLoad "ABOUT" wxBITMAP_TYPE_ICO_RESOURCE (sz 16 16) topLevelWindowSetIcon f ico_about Any advice? Thanks, Bernd |
From: shelarcy <she...@gm...> - 2009-01-05 00:55:11
|
On Mon, 05 Jan 2009 09:19:59 +0900, Günther Schmidt <re...@fe...> wrote: > this is a translation from the German error message: > > "The application could not be properly initialized, click on OK to > terminate the application". > > Error Code: "0xc0150002". Okay. How about install Microsoft Visual C++ 2008 SP1 Redistributable Package? http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
From: Günther S. <re...@fe...> - 2009-01-05 00:20:19
|
Hi, this is a translation from the German error message: "The application could not be properly initialized, click on OK to terminate the application". Error Code: "0xc0150002". Best regards Günther this is on Win XP Pro, ghc-6.10.1, latest binary package from your site. Am 05.01.2009, 01:00 Uhr, schrieb shelarcy <she...@gm...>: > Hi, > > On Mon, 05 Jan 2009 02:41:59 +0900, Günther Schmidt <re...@fe...> > wrote: >> I'm using ghc 6.10 here and tried to run the samples. Now I did >> understand >> the wouldn't run in ghci and so I compiled them. >> >> They do compile, the just won't run (on Windows XP), it immediately >> aborts >> with an error message about not being able to properly initialize the >> application. > > Please show us your error messages. It seems that this problem is the > same as older version's problem. But we don't know this problem is > actually same without error message and error number. > > http://haskell.org/haskellwiki/WxHaskell/Troubleshooting#Runtime_issues > > > Best Regards, > -- Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/ |
From: shelarcy <she...@gm...> - 2009-01-05 00:00:47
|
Hi, On Mon, 05 Jan 2009 02:41:59 +0900, Günther Schmidt <re...@fe...> wrote: > I'm using ghc 6.10 here and tried to run the samples. Now I did understand > the wouldn't run in ghci and so I compiled them. > > They do compile, the just won't run (on Windows XP), it immediately aborts > with an error message about not being able to properly initialize the > application. Please show us your error messages. It seems that this problem is the same as older version's problem. But we don't know this problem is actually same without error message and error number. http://haskell.org/haskellwiki/WxHaskell/Troubleshooting#Runtime_issues Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
From: Günther S. <re...@fe...> - 2009-01-04 17:42:16
|
Hi, I just read the announcement for 0.11.1 and of course immediately downloaded it. I'm using ghc 6.10 here and tried to run the samples. Now I did understand the wouldn't run in ghci and so I compiled them. They do compile, the just won't run (on Windows XP), it immediately aborts with an error message about not being able to properly initialize the application. What am I doing wrong? Günther |
From: Jeremy O'D. <jer...@gm...> - 2009-01-04 15:35:59
|
The wxHaskell development team is pleased to announce the release of wxHaskell 0.11.1, a Haskell binding for the wxWidgets GUI library. The Haskell support is built on a reasonably complete C language binding, which could be used as the basis for wxWidgets support on other languages/platforms which do not have easy mechanisms for linking with C++ code. The main highlights of wxHaskell 0.11.1 are: - Support for XRC resource files, allowing GUI design using a visual tool. Note that this is currently not type safe, and programs will crash if a widget is not cast to the correct type on loading. - Support for wxWidgets 2.8.x. Support for wxWidgets 2.4.2 is now dropped and wxHaskell will not compile against versions of wxWidgets prior to 2.6. This means that exploratory development using GHCi is no longer possible. Workaround is to continue to use older wxHaskell versions. - Support for GHC 6.10 - Preliminary support for Cabal / Hackage The full list of changes is provided at the end of this mail. Binary packages are available from the wxHaskell download site at http://sourceforge.net/project/showfiles.php?group_id=73133, for the following platforms: - Windows - OS X (Intel platform only) - Source code .tar.gz and .zip - Documentation (cross-platform) The wxHaskell libraries (wxcore and wx) are also available from Hackage (http://hackage.haskell.org). About wxHaskell --------------- wxHaskell is a Haskell binding to the wxWidgets GUI library for recent versions of the Glasgow Haskell Compiler. It provides a native look and feel on Windows, OS X and Linux, and a medium level programming interface. The main project page for wxHaskell is at http://wxhaskell.sourceforge.net. The latest source code for wxHaskell can always be obtained from http://darcs.haskell.org/wxhaskell. There are developer (wxh...@li... and user (wxh...@li...) mailing lists, and a wiki page at http://haskell.org/haskellwiki/WxHaskell which can provide more information to those interested. The C language binding for wxHaskell was derived from an original C language binding created for the Eiffel programming language by the ELJ project (http://elj.sourceforge.net). Non backward compatible changes: - Preliminary Cabal / Hackage support - Added "--global" argument to configure script - Added "--user" argument to configure script - Changed wxhaskell official web page to Haskell wiki at http://haskell.org/haskellwiki/WxHaskell - Changed official darcs repository to code.haskell.org - Adapted the wxHaskell C-layer to work with wxWidgets 2.8 - Adapted some part of wxcore API to be able to refer to wxWidgets 2.8 documentation for wxcore functions - Added "TopLevelWindow", which mainly removes some functionality from "Frame" - Changed "--with-stc" argument to "--with-contrib" - Removed "Wave" type synonym Backward compatible additions: - Added support for using XRC resource files to load most controls and menus attached to frames. - Added sample file showing how to use XRC support to attach command handlers to menu items - Added sample file showing how to use properties with many controls. - Added "--enable-optimization" argument to configure script - Added "--O*" argument to configure script - Added "--enable-library-profiling" argument to configure script - Added "--p" argument to configure script - Added "-fvia-C" argument to configure script. And moved this compilation flag to configure script - Added Image / ByteString conversion functions - Adapted the configuration to work with GHC 6.10. - Changed "Var" type synonym from "IORef" to stm's "TVar" for thread safety - Changed "imageGetPixelArray" and "imageCreateFromPixelArray" to be more flexible. - Changed "Point", "Size", "Vector" and "Rect" to be type synonym. - Added "wxcMilliSleep". Now, "wxcAppUSleep" is deprecated. Use "wxcMilliSleep" instead - Added very experimental wxGraphicsContext support - Added wxSVGFileDC functions Bugfixes: - Applied DEPRECATED pragma to old deprecated functions. Just documented in Haddock before. - Fixed "processExecAsync" hangs Windows GUI-only program - Fixed Windows binary install problem when path with spaces (bug 1400488) - Probably fixed the applicattion failed to initialize properly when using Windows binary. -- Jeremy O'Donoghue jer...@gm... -- Jeremy O'Donoghue jer...@gm... |
From: shelarcy <she...@gm...> - 2009-01-02 22:41:46
|
Hi, On Mon, 29 Dec 2008 08:30:05 +0900, Bernd Holzmüller <ber...@ic...> wrote: > Now, this seems not to be possible yet for toolbar icons. The function > "toolMenu" expects a file path argument, and there is no other function > that accepts a bitmap instead. I therefore suggest extending the file > Graphics.UI.WX.Menu.hs by an additional function: > toolMenuFromBitmap :: ToolBar a -> MenuItem a -> String -> Bitmap b -> > [Prop ToolBarItem] -> IO ToolBarItem > The signature of the present toolMenu function is: > toolMenu :: ToolBar a -> MenuItem a -> String -> FilePath -> [Prop > ToolBarItem] -> IO ToolBarItem > whose definition would then just reduce to > toolMenu toolbar menuitem label bitmapPath props = > withBitmapFromFile bitmapPath $ \bitmap -> toolMenuFromBitmap > toolbar menuitem label bitmap props I added toolMenuFromBitmap function in the darcs repository, and I replaced source and binary distribution by newer version now. http://www.mail-archive.com/wxh...@li.../msg00392.html Replacing distribution isn't good solution. So, this is final change before wxHaskell 0.11.0 release. If you want to use more new features, please wait for next next version. Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
From: Jeremy O'D. <je...@o-...> - 2008-12-29 09:53:55
|
Hi Günther, I used wxFormBuilder to create the sample code demonstrating XRC support, but you should be able to use anything which generates the XML representation of XRC. Some tools (e.g. wxFormBuilder), generate C++ by default, but can be configured to generate XML output, so you may need to change the default configuration. The DialogBlocks website feature list implies that it should work, but I doubt that anyone has tried it. You may want to try wxFormBuilder if you don't already have a copy of DialogBlocks - it's free and I found it to be pretty good. Regards Jeremy On 25 Dec 2008, at 18:22, Günther Schmidt wrote: > Hi, > > can I use DialogBlocks to design the UI, safe it to XML, and then > import > it into Haskell? > > Günther > > > ---------------------------------------------------------------------- > -------- > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users |
From: Bernd H. <ber...@ic...> - 2008-12-28 23:30:15
|
Hi all, I want to embed icons into an application by using resources under Windows. I understand how to prepare a resource file with entries like ico_about ICON "sm-bitmaps/about.ico" compile this file using windres (located in ghc-6.10.1/bin) and link the resulting object file with my application. In my application code I can then e.g. associate the about-icon with the application like so: ico_about <- iconCreateLoad "ico_about" wxBITMAP_TYPE_ICO_RESOURCE (sz 16 16) topLevelWindowSetIcon f ico_about Now, this seems not to be possible yet for toolbar icons. The function "toolMenu" expects a file path argument, and there is no other function that accepts a bitmap instead. I therefore suggest extending the file Graphics.UI.WX.Menu.hs by an additional function: toolMenuFromBitmap :: ToolBar a -> MenuItem a -> String -> Bitmap b -> [Prop ToolBarItem] -> IO ToolBarItem The signature of the present toolMenu function is: toolMenu :: ToolBar a -> MenuItem a -> String -> FilePath -> [Prop ToolBarItem] -> IO ToolBarItem whose definition would then just reduce to toolMenu toolbar menuitem label bitmapPath props = withBitmapFromFile bitmapPath $ \bitmap -> toolMenuFromBitmap toolbar menuitem label bitmap props Best regards, Bernd P.S. Unfortunately, I cannot define the function toolMenuFromBitmap in my application because the data constructor ToolBarItem is not exported from Menu! |
From: shelarcy <she...@gm...> - 2008-12-27 00:09:05
|
Hi, On Fri, 26 Dec 2008 07:25:01 +0900, Bernd Holzmüller <ber...@ic...> wrote: > I found one bug (on Windows XP) concerning the layout of Notebooks: > wxNB_BOTTOM now places tabs to the right, wxNB_LEFT places tabs at the > bottom, wxNB_RIGHT places tabs at the left :-) I fixed this bug and I replaced sourceforge file by newer version now. Please try to use newer version. http://www.mail-archive.com/wxh...@li.../msg00386.html Best Regards, -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/ |
From: Bernd H. <ber...@ic...> - 2008-12-25 22:25:08
|
Hi all, thanks for preparing this new wxHaskell version! I found one bug (on Windows XP) concerning the layout of Notebooks: wxNB_BOTTOM now places tabs to the right, wxNB_LEFT places tabs at the bottom, wxNB_RIGHT places tabs at the left :-) Best regards, Bernd |