wxhaskell-devel — wxhaskell developers

[wxhaskell-devel] Who is reviewing and committing patches

[Mads L. <mad...@gm...>]

Hi All,

Who is committing and reviewing patches these days?

I have made two fixes, which is attached to this email. One is for a fix 
that both David Rogers and I experienced. See 
http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/1278 
and http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.devel/861.

The other fix is to make wxHaskell compile on GHC 7.6.1.

I made the patches using:

> darcs send --output "patch_name" --author "Mads Lindstroem" --from "Mads Lindstroem" -i


Greetings,

Mads Lindstrøm

[wxhaskell-devel] Compile Error

[David R. <pre...@gm...>]

Very recently, I installed wxc-0.90.0.4 and defeated a compile error
building on the libgtk-3-dev package in Ubuntu (and a manually installed
wxWidgets-2.9.4).  The trouble started because gcc 4.6.3 errored out on a
line:
    *_ref = NULL;
claiming it didn't know what a wxBitmap was.

This traces to
/usr/local/include/wx-2.9/wx/gtk/bitmap.h : which included two definitions:
    wxBitmap( const char* const* bits );
    wxBitmap(GdkPixbuf* pixbuf);

I picked one by modifying line 159 of
src/cpp/eljpen.cpp : to read
EWXWEXPORT(void,wxPen_GetStipple)(void* self,wxBitmap* _ref)
{
#if defined(__WXGTK__)
    *_ref = wxBitmap((const char* const*)NULL);
#else
    *_ref = *(((wxPen*)self)->GetStipple());
#endif
}

and the thing compiled.

~ David M. Rogers

[wxhaskell-devel] [ wxhaskell-Bugs-3593602 ] FileBrowse.hs sample crashes

[SourceForge.net <no...@so...>]

Bugs item #3593602, was opened at 2012-12-07 04:08
Message generated for change (Tracker Item Submitted) made by atzedijkstra
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3593602&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Atze Dijkstra (atzedijkstra)
Assigned to: Nobody/Anonymous (nobody)
Summary: FileBrowse.hs sample crashes

Initial Comment:
On MacOSX 10.8, wx-0.90.0.1, ghc 7.4.1, I tried to run http://code.haskell.org/wxhaskell/samples/wx/FileBrowse.hs but it crashes. When trying various treeCtrl functions in an isolated setting (copying code from the sample) a crash did occur as soon treeCtrlAppendItem was called.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3593602&group_id=73133

[wxhaskell-devel] [ wxhaskell-Bugs-3576397 ] wxc-0.90.0.4 + WxWidgets 2.9 install problem

[SourceForge.net <no...@so...>]

Bugs item #3576397, was opened at 2012-10-11 10:49
Message generated for change (Tracker Item Submitted) made by mike-delorimier
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3576397&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael deLorimier (mike-delorimier)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxc-0.90.0.4 + WxWidgets 2.9 install problem

Initial Comment:
I'm trying to install reactive-banana-wx, but wxc won't compile.

When I try
  cabal install wxc
I get a C++ compile error.

Making cabal constraints explicit shows me that this error occurs for wxc-0.90.0.1 through wxc-0.90.0.4

My WxWidgets library is 2.9 and I installed it from a tarball (since it doesn't have a debian package).
cabal --version = 0.14.0  My cabal constraint file is the default.
ghc --version = 7.4.1
gcc --version = (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
OS version:
michael-x201% cat /proc/version
Linux version 3.2.0-31-generic (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012

Also, the bad code is in a #ifdef case when the __WXGTK__ flag is enabled.

The C++ compiler error is:
/usr/bin/gcc -Wl,--hash-size=31 -Wl,--reduce-memory-overheads -Isrc/incl
ude -I/usr/local/include/wx-2.9 -I/usr/local/lib/wx/include/gtk2-unicode
-2.9 -D__WXGTK__ -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -DwxcREFUSE_MEDIACT
RL -fPIC -c src/cpp/eljpen.cpp -o dist/build/src/cpp/eljpen.o
src/cpp/eljpen.cpp: In function ‘void wxPen_GetStipple(void*, wxBitmap*)
’:
src/cpp/eljpen.cpp:159:13: error: conversion from ‘long int’ to ‘const w
xBitmap’ is ambiguous
src/cpp/eljpen.cpp:159:13: note: candidates are:
/usr/local/include/wx-2.9/wx/gtk/bitmap.h:83:5: note: wxBitmap::wxBitmap
(GdkPixbuf*)  
/usr/local/include/wx-2.9/wx/gtk/bitmap.h:73:5: note: wxBitmap::wxBitmap
(const char* const*)
/usr/local/include/wx-2.9/wx/gtk/bitmap.h:64:24: error:   initializing a
rgument 1 of ‘wxBitmap& wxBitmap::operator=(const wxBitmap&)’

The offending code, in file src/cpp/eljpen.cpp, is:
EWXWEXPORT(void,wxPen_GetStipple)(void* self,wxBitmap* _ref)
{
#if defined(__WXGTK__)
    *_ref = NULL;
#else
    *_ref = *(((wxPen*)self)->GetStipple());
#endif
}

To get it to compile I replaced the NULL on line 159 with wxBitmap();
Some examples in reactive-banana-wx now run so my fix didn't break everything.

So what's the problem? I'm pretty sure the wx 2.9 library it's using is the right one. Did no one check the __WXGTK__ case?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3576397&group_id=73133

[wxhaskell-devel] [ wxhaskell-Bugs-3574828 ] Error starting wxhaskell executables

[SourceForge.net <no...@so...>]

Bugs item #3574828, was opened at 2012-10-05 08:55
Message generated for change (Tracker Item Submitted) made by siodine
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3574828&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: siodine (siodine)
Assigned to: Nobody/Anonymous (nobody)
Summary: Error starting wxhaskell executables

Initial Comment:
---------------------------
test.exe - Application Error
---------------------------
The application was unable to start correctly (0xc0000142). Click OK to close the application. 
---------------------------
OK   
---------------------------

This is on Windows 8, wx-0.90.0.1, wxc-0.90.0.4, wxcore-0.90.0.3, wxdirect-0.90.0.1, wxWidgets 2.9.4. wxWidgets C++ samples compiled with mingw do not have this error. Programs compiled with old wxhaskell (latest version to support wxWidgets 2.8) do work.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3574828&group_id=73133

[wxhaskell-devel] [ wxhaskell-Bugs-3572834 ] cabal install fails on wx-0.13.2.1

[SourceForge.net <no...@so...>]

Bugs item #3572834, was opened at 2012-09-28 10:33
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3572834&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: cabal install fails on wx-0.13.2.1

Initial Comment:
When I run either 

$ cabal install 'wx < 0.9'

or

$ cabal install wx-0.13.2.1

cabal fails while trying to build wxcore 0.9.x (sorry I don't have the exact error message anymore).

 Details: 

I'm running Ubuntu 12.04.1 and followed http://www.haskell.org/haskellwiki/WxHaskell/Linux
(so libwxgtk2.8-dev is installed).

One would expect cabal to try to build wxcore of some version 0.13.x or 0.12.x.
It turns out that in the cabal file for wx-0.13.2.1, the constraint for wx-core is '>=  0.12.1.6' in the normal case, and  '>=0.13.1' if the splitBase flag is set. 

I edited the cabal file appending ''&& < 0.90' to both constraints. Then 'cabal install' worked.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3572834&group_id=73133

[wxhaskell-devel] Update needed for the wxdirect and wxcore packages

[Henk-Jan v. T. <hj...@ch...>]

L.S.,

The wxdirect and wxcore packages depend on containers (≥0.2 & <0.5); as  
GHC 7.6.1 comes with containers-0.5.0.0, this causes problems (dependency  
conflicts) with packages that use the latest version of containers. Please  
update wxdirect.cabal and wxcore.cabal to allow for containers-0.5

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

[wxhaskell-devel] UI updates from non-UI threads: an addition to wx?

[<mac...@gm...>]

Getting wxHaskell to handle UI updates from non-UI threads was a
frustrating experience; it's embarassing how long it took me to
realise that the solution presented in this StackOverflow answer:
http://stackoverflow.com/a/3182588/424978 is probably the only viable
one. I've packaged it into a tiny module that provides Gtk2hs-style
`postGUIAsync` function:
https://github.com/mmakowski/habaz/blob/master/src/Graphics/UI/WX/Async.hs.
Is there any interest in incorporating this into wxHaskell proper? It
might save other users some head scratching.

Regards,
Maciek

Re: [wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

RESULT/S:

-  Managed to get wxcore and wxc installed and working, to helloworld level, based on the latest github master. 

- All Eric's helloworld examples now compile and generally work, incl. wxcore and wx versions, without the link error problem posted below.

Henrys-iMac:wx henrylockyer$ ghc-pkg list --user
/Users/henrylockyer/.ghc/x86_64-darwin-7.0.4/package.conf.d
   MissingH-1.1.1.0
   cabal-macosx-0.2.2
   hslogger-1.1.5
   strict-0.3.2
   wx-0.90.0.1       
   wxc-0.90.0.4      <====<<<
   wxcore-0.90.0.3  <====<<<
   wxdirect-0.90.0.1

- A couple of weird things I encountered which are probably due to pilot error somewhere (I've not used the
 'runhaskell Setup configure/build/install' method before) but I'll mention them in case they indicate something 
  that should be attended to:

      	a) When building wxc, registration of the pkg seemed to occur, as I expected, in the install phase, but when 
            building wxcore there was a message to say it had registered the pkg at the end of the build phase, I gave
            the install command and it then reported registering the pkg again. Seemed a little fishy.

        b) When it came to adding wx back in I went back to using cabal install to pull wx from hackage again, 
             but got the following message:

                     src/Graphics/UI/WX/Draw.hs:33:8:
                           Could not find module `Graphics.UI.WXCore':
                                 Perhaps you haven't installed the profiling libraries for package `wxcore-0.90.0.3'?
                                 Use -v to see a list of the files searched for.
                     cabal: Error: some packages failed to install:
                     wx-0.90.0.1 failed during the building phase. The exception was:
                     ExitFailure 1
 
              "-v" didn't tell me much but  --disable-library-profiling convinced cabal to install it.
              I thought the profiling option should have been defaulted 'off' during the build phase of wxc and wxcore
              as well as in the cabal install of wx -  I certainly didn't deliberately set any parameters in connection 
              with profiling.

Annoyingly I accidentally closed the terminal without saving, so can't post more specific detail or check my eyesight.

Regards/ Henry 


On 30 Jun 2012, at 18:53, Henry Lockyer wrote:

> Sorry - I was really meaning 'included in Hackage' so that I could use 'cabal install', in case that wasn't obvious.
> 
> I see, superficially at least, everything seems to be there on github master for wxc 0.90.04 and wxcore 0.90.04, 
> so I'll have a go at installing these 'manually' (wx seems to be the same version but will also need to be rebuilt 
> after presumably).  
> 
> /Henry
>  
> On 30 Jun 2012, at 16:54, Henry Lockyer wrote:
> 
>> Is the cabalistic version of wxcore 0.90.0.3 still imminent or has life intervened? 
>> If it's not likely for a while then I guess I'd better get my swimming trunks on and head for the shallow end of Github ;-)
>> Regards/ Henry
>> 
>> On 27 Jun 2012, at 17:48, Jeremy O'Donoghue wrote:
>> 
>>> I think you did the right thing. We'll debug further if the Cabal update doesn't work for you.
>>> 
>>> Regards
>>> Jeremy
>>> 
>>> On 27 June 2012 16:46, Henry Lockyer <hen...@nt...> wrote:
>>> ok + thanks. I guess I'll wait for updated cabal if it is imminent .
>>> Re (1) I could double-check this in the meantime perhaps, but what to look for exactly? 
>>> (I relied on "cabal install wx cabal-macosx" on an empty local user pkg lib to get it right.)
>>> Regards/ Henry
>>> 
>>> On 27 Jun 2012, at 15:28, Jeremy O'Donoghue wrote:
>>> 
>>>> There are a couple of possibilities:
>>>> 
>>>> 1) (which I think can be discounted, given your description of 'removed everything and started again') is that you didn't do a clean build. The dependency checking for wxc is rather fragile (bacause Cabal does not know about C dependencies).
>>>> 2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this was bumped when I messed up some dependencies in one of the releases (I didn't notice because *I* hadn't cleaned up properly before testing. Have you tried pulling from the tip of the master branch on Github in the past few days (I commited the updates to Github on June 10th - haven't updated cabal yet as I have been too busy - will try to do so this evening (UK time).
>>>> 
>>>> In other words, I think this may be my fault, for which my sincere apologies.
>>>> 
>>>> Best regards
>>>> Jeremy
>>>> 
>>>> On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:
>>>> Hello - is this a fault with wxc (or associates) ? 
>>>> 
>>>> Cannot build Eric's wxcore 'HelloWorld' (from https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs ) 
>>>> due to "Undefined symbols".
>>>> 
>>>> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8 snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
>>>> 
>>>> I discovered some legacy mess in the local pkg installations so removed everything from --user pkgs and rebuilt it all again 
>>>> cleanly with cabal install, with no apparent errors at this stage. The install looks fine now but I still get the same error and am now stuck..
>>>> 
>>>> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
>>>> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
>>>> Linking HelloWorld ...
>>>> Undefined symbols:
>>>>   "_wxListItemAttr_SetTextColour", referenced from:
>>>>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_Create", referenced from:
>>>>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>>>>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrl_RefreshItem", referenced from:
>>>>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>>>>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_Create", referenced from:
>>>>       _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>>>>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_CreateEx", referenced from:
>>>>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>>>>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrl_IsVirtual", referenced from:
>>>>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrl_GetItemFont", referenced from:
>>>>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_SetFont", referenced from:
>>>>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>>>>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_GetTextColor", referenced from:
>>>>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_GetFont", referenced from:
>>>>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_HasFont", referenced from:
>>>>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>>>>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>>>>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_HasTextColour", referenced from:
>>>>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>>>>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>> ld: symbol(s) not found
>>>> collect2: ld returned 1 exit status
>>>> 
>>>> Thanks/ Henry
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>> will include endpoint security, mobile security and the latest in malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> wxhaskell-devel mailing list
>>>> wxh...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>>>> 
>>>> 
>>> 
>>> 
>> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> wxhaskell-devel mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

Re: [wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

Sorry - I was really meaning 'included in Hackage' so that I could use 'cabal install', in case that wasn't obvious.

I see, superficially at least, everything seems to be there on github master for wxc 0.90.04 and wxcore 0.90.04, 
so I'll have a go at installing these 'manually' (wx seems to be the same version but will also need to be rebuilt 
after presumably).  

/Henry
 
On 30 Jun 2012, at 16:54, Henry Lockyer wrote:

> Is the cabalistic version of wxcore 0.90.0.3 still imminent or has life intervened? 
> If it's not likely for a while then I guess I'd better get my swimming trunks on and head for the shallow end of Github ;-)
> Regards/ Henry
> 
> On 27 Jun 2012, at 17:48, Jeremy O'Donoghue wrote:
> 
>> I think you did the right thing. We'll debug further if the Cabal update doesn't work for you.
>> 
>> Regards
>> Jeremy
>> 
>> On 27 June 2012 16:46, Henry Lockyer <hen...@nt...> wrote:
>> ok + thanks. I guess I'll wait for updated cabal if it is imminent .
>> Re (1) I could double-check this in the meantime perhaps, but what to look for exactly? 
>> (I relied on "cabal install wx cabal-macosx" on an empty local user pkg lib to get it right.)
>> Regards/ Henry
>> 
>> On 27 Jun 2012, at 15:28, Jeremy O'Donoghue wrote:
>> 
>>> There are a couple of possibilities:
>>> 
>>> 1) (which I think can be discounted, given your description of 'removed everything and started again') is that you didn't do a clean build. The dependency checking for wxc is rather fragile (bacause Cabal does not know about C dependencies).
>>> 2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this was bumped when I messed up some dependencies in one of the releases (I didn't notice because *I* hadn't cleaned up properly before testing. Have you tried pulling from the tip of the master branch on Github in the past few days (I commited the updates to Github on June 10th - haven't updated cabal yet as I have been too busy - will try to do so this evening (UK time).
>>> 
>>> In other words, I think this may be my fault, for which my sincere apologies.
>>> 
>>> Best regards
>>> Jeremy
>>> 
>>> On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:
>>> Hello - is this a fault with wxc (or associates) ? 
>>> 
>>> Cannot build Eric's wxcore 'HelloWorld' (from https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs ) 
>>> due to "Undefined symbols".
>>> 
>>> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8 snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
>>> 
>>> I discovered some legacy mess in the local pkg installations so removed everything from --user pkgs and rebuilt it all again 
>>> cleanly with cabal install, with no apparent errors at this stage. The install looks fine now but I still get the same error and am now stuck..
>>> 
>>> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
>>> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
>>> Linking HelloWorld ...
>>> Undefined symbols:
>>>   "_wxListItemAttr_SetTextColour", referenced from:
>>>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_Create", referenced from:
>>>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>>>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrl_RefreshItem", referenced from:
>>>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>>>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_Create", referenced from:
>>>       _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>>>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_CreateEx", referenced from:
>>>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>>>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrl_IsVirtual", referenced from:
>>>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrl_GetItemFont", referenced from:
>>>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_SetFont", referenced from:
>>>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>>>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_GetTextColor", referenced from:
>>>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_GetFont", referenced from:
>>>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_HasFont", referenced from:
>>>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>>>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>>>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_HasTextColour", referenced from:
>>>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>>>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>> ld: symbol(s) not found
>>> collect2: ld returned 1 exit status
>>> 
>>> Thanks/ Henry
>>> 
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> wxhaskell-devel mailing list
>>> wxh...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>>> 
>>> 
>> 
>> 
> 

Re: [wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

Is the cabalistic version of wxcore 0.90.0.3 still imminent or has life intervened? 
If it's not likely for a while then I guess I'd better get my swimming trunks on and head for the shallow end of Github ;-)
Regards/ Henry

On 27 Jun 2012, at 17:48, Jeremy O'Donoghue wrote:

> I think you did the right thing. We'll debug further if the Cabal update doesn't work for you.
> 
> Regards
> Jeremy
> 
> On 27 June 2012 16:46, Henry Lockyer <hen...@nt...> wrote:
> ok + thanks. I guess I'll wait for updated cabal if it is imminent .
> Re (1) I could double-check this in the meantime perhaps, but what to look for exactly? 
> (I relied on "cabal install wx cabal-macosx" on an empty local user pkg lib to get it right.)
> Regards/ Henry
> 
> On 27 Jun 2012, at 15:28, Jeremy O'Donoghue wrote:
> 
>> There are a couple of possibilities:
>> 
>> 1) (which I think can be discounted, given your description of 'removed everything and started again') is that you didn't do a clean build. The dependency checking for wxc is rather fragile (bacause Cabal does not know about C dependencies).
>> 2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this was bumped when I messed up some dependencies in one of the releases (I didn't notice because *I* hadn't cleaned up properly before testing. Have you tried pulling from the tip of the master branch on Github in the past few days (I commited the updates to Github on June 10th - haven't updated cabal yet as I have been too busy - will try to do so this evening (UK time).
>> 
>> In other words, I think this may be my fault, for which my sincere apologies.
>> 
>> Best regards
>> Jeremy
>> 
>> On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:
>> Hello - is this a fault with wxc (or associates) ? 
>> 
>> Cannot build Eric's wxcore 'HelloWorld' (from https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs ) 
>> due to "Undefined symbols".
>> 
>> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8 snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
>> 
>> I discovered some legacy mess in the local pkg installations so removed everything from --user pkgs and rebuilt it all again 
>> cleanly with cabal install, with no apparent errors at this stage. The install looks fine now but I still get the same error and am now stuck..
>> 
>> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
>> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
>> Linking HelloWorld ...
>> Undefined symbols:
>>   "_wxListItemAttr_SetTextColour", referenced from:
>>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_Create", referenced from:
>>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_RefreshItem", referenced from:
>>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_Create", referenced from:
>>       _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_CreateEx", referenced from:
>>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_IsVirtual", referenced from:
>>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_GetItemFont", referenced from:
>>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_SetFont", referenced from:
>>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetTextColor", referenced from:
>>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetFont", referenced from:
>>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasFont", referenced from:
>>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasTextColour", referenced from:
>>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>> ld: symbol(s) not found
>> collect2: ld returned 1 exit status
>> 
>> Thanks/ Henry
>> 
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> wxhaskell-devel mailing list
>> wxh...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>> 
>> 
> 
> 

Re: [wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

Hi Eric
Yes I have been essentially following that as a rational approach (though I guess you mean wxWidgets, wxcore, wx ) and I have used all your samples (thanks!).
It's good to have a potted example to check out each level.

I realise your readme instructions are skeletal but maybe worth adding that wxWidgets 'minimal' needs the "samples.xpm" file in the src dir (or equiv.). 
(An alternative wxWidgets version at http://wxwidgets.org/docs/tutorials/hworld.txt  does not need this.)

On macos another gratifying basic test is applying macosx-app and launching from finder (or open).

Regards/ Henry


On 27 Jun 2012, at 16:59, Eric Kow wrote:

> Out of interest (sorry, not following thread), has the 3-step testing approach (wxc, wxcore, wx) in my minimal tester been useful at all?
> 
> Thanks,
> 
> Eric
> 
> On 27 Jun 2012, at 16:46, Henry Lockyer wrote:
> 
>> ok + thanks. I guess I'll wait for updated cabal if it is imminent .
>> Re (1) I could double-check this in the meantime perhaps, but what to look for exactly? 
>> (I relied on "cabal install wx cabal-macosx" on an empty local user pkg lib to get it right.)
> 
> -- 
> Eric Kow <http://erickow.com>
> 

Re: [wxhaskell-devel] wxc/ore? linking problem

[Jeremy O'D. <jer...@gm...>]

I think you did the right thing. We'll debug further if the Cabal update
doesn't work for you.

Regards
Jeremy

On 27 June 2012 16:46, Henry Lockyer <hen...@nt...> wrote:

> ok + thanks. I guess I'll wait for updated cabal if it is imminent .
> Re (1) I could double-check this in the meantime perhaps, but what to look
> for exactly?
> (I relied on "cabal install wx cabal-macosx" on an empty local user pkg
> lib to get it right.)
> Regards/ Henry
>
> On 27 Jun 2012, at 15:28, Jeremy O'Donoghue wrote:
>
> There are a couple of possibilities:
>
> 1) (which I think can be discounted, given your description of 'removed
> everything and started again') is that you didn't do a clean build. The
> dependency checking for wxc is rather fragile (bacause Cabal does not know
> about C dependencies).
> 2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this
> was bumped when I messed up some dependencies in one of the releases (I
> didn't notice because *I* hadn't cleaned up properly before testing. Have
> you tried pulling from the tip of the master branch on Github in the past
> few days (I commited the updates to Github on June 10th - haven't updated
> cabal yet as I have been too busy - will try to do so this evening (UK
> time).
>
> In other words, I think this may be my fault, for which my sincere
> apologies.
>
> Best regards
> Jeremy
>
> On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:
>
>> Hello - is this a fault with wxc (or associates) ?
>>
>> Cannot build Eric's wxcore 'HelloWorld' (from
>> https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs
>>  )
>> due to "Undefined symbols".
>>
>> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8
>> snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
>>
>> I discovered some legacy mess in the local pkg installations so removed
>> everything from --user pkgs and rebuilt it all again
>> cleanly with cabal install, with no apparent errors at this stage. The
>> install looks fine now but I still get the same error and am now stuck..
>>
>> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
>> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
>> Linking HelloWorld ...
>> Undefined symbols:
>>   "_wxListItemAttr_SetTextColour", referenced from:
>>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_Create", referenced from:
>>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_RefreshItem", referenced from:
>>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_Create", referenced from:
>>
>> _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info
>> in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_CreateEx", referenced from:
>>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_IsVirtual", referenced from:
>>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrl_GetItemFont", referenced from:
>>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_SetFont", referenced from:
>>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetTextColor", referenced from:
>>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_GetFont", referenced from:
>>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasFont", referenced from:
>>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasTextColour", referenced from:
>>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>> ld: symbol(s) not found
>> collect2: ld returned 1 exit status
>>
>> Thanks/ Henry
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> wxhaskell-devel mailing list
>> wxh...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>>
>>
>
>

Re: [wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

ok + thanks. I guess I'll wait for updated cabal if it is imminent .
Re (1) I could double-check this in the meantime perhaps, but what to look for exactly? 
(I relied on "cabal install wx cabal-macosx" on an empty local user pkg lib to get it right.)
Regards/ Henry

On 27 Jun 2012, at 15:28, Jeremy O'Donoghue wrote:

> There are a couple of possibilities:
> 
> 1) (which I think can be discounted, given your description of 'removed everything and started again') is that you didn't do a clean build. The dependency checking for wxc is rather fragile (bacause Cabal does not know about C dependencies).
> 2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this was bumped when I messed up some dependencies in one of the releases (I didn't notice because *I* hadn't cleaned up properly before testing. Have you tried pulling from the tip of the master branch on Github in the past few days (I commited the updates to Github on June 10th - haven't updated cabal yet as I have been too busy - will try to do so this evening (UK time).
> 
> In other words, I think this may be my fault, for which my sincere apologies.
> 
> Best regards
> Jeremy
> 
> On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:
> Hello - is this a fault with wxc (or associates) ? 
> 
> Cannot build Eric's wxcore 'HelloWorld' (from https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs ) 
> due to "Undefined symbols".
> 
> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8 snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
> 
> I discovered some legacy mess in the local pkg installations so removed everything from --user pkgs and rebuilt it all again 
> cleanly with cabal install, with no apparent errors at this stage. The install looks fine now but I still get the same error and am now stuck..
> 
> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
> Linking HelloWorld ...
> Undefined symbols:
>   "_wxListItemAttr_SetTextColour", referenced from:
>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_Create", referenced from:
>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_RefreshItem", referenced from:
>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_Create", referenced from:
>       _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_CreateEx", referenced from:
>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_IsVirtual", referenced from:
>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_GetItemFont", referenced from:
>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_SetFont", referenced from:
>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetTextColor", referenced from:
>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetFont", referenced from:
>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasFont", referenced from:
>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasTextColour", referenced from:
>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> 
> Thanks/ Henry
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> wxhaskell-devel mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
> 
> 

Re: [wxhaskell-devel] wxc/ore? linking problem

[Jeremy O'D. <jer...@gm...>]

There are a couple of possibilities:

1) (which I think can be discounted, given your description of 'removed
everything and started again') is that you didn't do a clean build. The
dependency checking for wxc is rather fragile (bacause Cabal does not know
about C dependencies).
2) More likely: the latest version of wxcore on Github is 0.90.0.3 - this
was bumped when I messed up some dependencies in one of the releases (I
didn't notice because *I* hadn't cleaned up properly before testing. Have
you tried pulling from the tip of the master branch on Github in the past
few days (I commited the updates to Github on June 10th - haven't updated
cabal yet as I have been too busy - will try to do so this evening (UK
time).

In other words, I think this may be my fault, for which my sincere
apologies.

Best regards
Jeremy

On 27 June 2012 13:38, Henry Lockyer <hen...@nt...> wrote:

> Hello - is this a fault with wxc (or associates) ?
>
> Cannot build Eric's wxcore 'HelloWorld' (from
> https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs
>  )
> due to "Undefined symbols".
>
> This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8
> snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).
>
> I discovered some legacy mess in the local pkg installations so removed
> everything from --user pkgs and rebuilt it all again
> cleanly with cabal install, with no apparent errors at this stage. The
> install looks fine now but I still get the same error and am now stuck..
>
> Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
> Linking HelloWorld ...
> Undefined symbols:
>   "_wxListItemAttr_SetTextColour", referenced from:
>       _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_Create", referenced from:
>       _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetBackgroundColor", referenced from:
>       _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_RefreshItem", referenced from:
>       _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
>       _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_Create", referenced from:
>
> _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info
> in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
>       _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_CreateEx", referenced from:
>       _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_CreateWithCb", referenced from:
>       _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_IsVirtual", referenced from:
>       _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrl_GetItemFont", referenced from:
>       _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_SetFont", referenced from:
>       _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
>       _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetTextColor", referenced from:
>       _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_GetFont", referenced from:
>       _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasFont", referenced from:
>       _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_SetBackgroundColour", referenced from:
>       _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
>       _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasTextColour", referenced from:
>       _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>   "_wxListItemAttr_HasBackgroundColour", referenced from:
>       _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>       _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
>
> Thanks/ Henry
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> wxhaskell-devel mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
>
>

[wxhaskell-devel] wxc/ore? linking problem

[Henry L. <hen...@nt...>]

Hello - is this a fault with wxc (or associates) ? 

Cannot build Eric's wxcore 'HelloWorld' (from https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs ) 
due to "Undefined symbols".

This is based on an i86_64-only wxWidgets 2.9.3 build on mac os 10.6.8 snow leopard with xcode 3.2.6 and with ghc 7.0.4  (HP 2011.4.0.0 64).

I discovered some legacy mess in the local pkg installations so removed everything from --user pkgs and rebuilt it all again 
cleanly with cabal install, with no apparent errors at this stage. The install looks fine now but I still get the same error and am now stuck..

Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld
[1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
Linking HelloWorld ...
Undefined symbols:
  "_wxListItemAttr_SetTextColour", referenced from:
      _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_Create", referenced from:
      _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetBackgroundColor", referenced from:
      _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_RefreshItem", referenced from:
      _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
      _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_Create", referenced from:
      _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
      _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_CreateEx", referenced from:
      _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_CreateWithCb", referenced from:
      _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_IsVirtual", referenced from:
      _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_GetItemFont", referenced from:
      _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_SetFont", referenced from:
      _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
      _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetTextColor", referenced from:
      _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetFont", referenced from:
      _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasFont", referenced from:
      _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_SetBackgroundColour", referenced from:
      _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
      _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasTextColour", referenced from:
      _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasBackgroundColour", referenced from:
      _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status

Thanks/ Henry

[wxhaskell-devel] [ wxhaskell-Bugs-3536406 ] wxc-0.90.0.3 does not compile on Debian [fix supplied]

[SourceForge.net <no...@so...>]

Bugs item #3536406, was opened at 2012-06-19 13:19
Message generated for change (Tracker Item Submitted) made by alanz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3536406&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alan Zimmerman (alanz)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxc-0.90.0.3 does not compile on Debian [fix supplied]

Initial Comment:
wxc-0.90.0.3 fails to compile using ghc-7.4.1 on Debian testing.

I could get it to install by installing wx 2.9, and then wxc install would
fail with eljpen.cpp not compiling. I had to change line 159 to

 *_ref = ((const char* const*)NULL);

from

 *_ref = NULL;


After that it just installed.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3536406&group_id=73133

[wxhaskell-devel] [ wxhaskell-Bugs-3534448 ] Unavoidable beeping on enter inside text controls.

[SourceForge.net <no...@so...>]

Bugs item #3534448, was opened at 2012-06-11 14:58
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3534448&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Unavoidable beeping on enter inside text controls.

Initial Comment:
Press enter inside a textEntry and you'll receive a beep. processEnter, on command, and on anyKey do nothing to resolve the problem. This is on Windows 8 with wxcore and wx 0.13.2.1.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3534448&group_id=73133

[wxhaskell-devel] Running out of memory, installing wxcore

[Henk-Jan v. T. <hj...@ch...>]

L.S.,

Using my patched version of wxcore (see my previous e-mail), my system  
(Windows XP) runs out of memory (1 GiB real, 4 GiB virtual), when trying  
to install wxcore. See the session below.

C:\Haskell\Temp\wxcore-0.90.0.1>cabal install
Resolving dependencies...
Configuring wxcore-0.90.0.1...
Generating class type definitions from .h files
setup.exe: out of memory
cabal: Error: some packages failed to install:
wxcore-0.90.0.1 failed during the configure step. The exception was:
ExitFailure 1


Does anyone have the same experience? Any quick solution?

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

Re: [wxhaskell-devel] [wxhaskell-users] Problems installing wxcore (space in path)

[Henk-Jan v. T. <hj...@ch...>]

On Wed, 06 Jun 2012 23:14:20 +0200, Henk-Jan van Tuyl <hj...@ch...>  
wrote:

> The following session seems to indicate that the setup of wxcore cannot
> handle a space in the pathname of the directory where packages are
> installed. I don't know how to change the location of this directory; any
> suggestions how to get wxcore installed? (System: Windows XP)
>
>> cabal install wx --global
> Resolving dependencies...
> [1 of 1] Compiling Main             (
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\Setup.hs,
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\Main.o
> )
> Linking
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\setup.exe
> ...
> Configuring wxcore-0.90.0.1...
> Generating class type definitions from .h files
> generating: src/haskell/Graphics/UI/WXCore/WxcClassTypes.hs
> reading class definitions:
> parsing: C:\Program/include/wxc.h
> wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such  
> file
> or directory)
> Generating class info definitions
> generating: src/haskell/Graphics/UI/WXCore/WxcClassInfo.hs
> reading class definitions:
> parsing: C:\Program/include/wxc.h
> wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such  
> file
> or directory)
> Generating class method definitions from .h files
> parsing: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h
> wxdirect: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h: openFile:
> does not exist (No such file or directory)

I have found a solution; I changed wxcore-0.90.0.1\setup.hs (added double  
quotes before and after filenames):
  - line 57 changed to:
     let wxcoreIncludeFile = "\"" ++ wxcDirectory </> "include/wxc.h\""
  - inserted after line 57:
     let wxcDirectory      = "\"" ++ wxcDirectory ++ "\""

This solution should be tested on other platforms.

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

[wxhaskell-devel] SplitterWindow: SetSashGravity and GetSashGravity

[Henning T. <le...@he...>]

I have a patch for the WxWidgets-2.8 branch. It adds functions for 
setting the sash gravity. Without setting the gravity the default value 
is unusable on some configurations, resulting in splitterwindows where 
one part has zero width or height.

Where is the repository for that branch? I would like to add it to 
wxcore.cabal.

[wxhaskell-devel] [ wxhaskell-Bugs-3530781 ] wxc-0.90.0.3 don't compiles on Windows

[SourceForge.net <no...@so...>]

Bugs item #3530781, was opened at 2012-05-30 05:02
Message generated for change (Tracker Item Submitted) made by stranger1234
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3530781&group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: stranger1234 (stranger1234)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxc-0.90.0.3 don't compiles on Windows

Initial Comment:
Log says: "gcc.exe: error: unrecognized option '--dll'"

After replacing 
Windows -> ["--dll", "-shared",
to 
Windows -> ["-Wl,--dll", "-shared",
 in Setup.hs - it compiles.

Haskell Platform 2011.4.0.0 + tdm-gcc-4.6.1.exe

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=536845&aid=3530781&group_id=73133

[wxhaskell-devel] Build errors for wxHaskell

[Edward A. <edw...@gm...>]

I have just installed wxHaskell 2.9.3 on OS X Lion from source.

When I run cabal install wx, wxc building fails with the following error:

src/cpp/ewxw_main.cpp: In function ‘void
ELJApp_InitializeC(wxClosure*, int, char**)’:
src/cpp/ewxw_main.cpp:99: warning: deprecated conversion from string
constant to ‘char*’
src/cpp/ewxw_main.cpp:112: error: ‘wxPendingEvents’ was not declared
in this scope
src/cpp/ewxw_main.cpp: In function ‘void ELJApp_initialize(void*, bool
(*)(), int, void*)’:
src/cpp/ewxw_main.cpp:123: error: ‘wxPendingEvents’ was not declared
in this scope

[wxhaskell-devel] Design discussion - Composable Events

[Heinrich A. <apf...@qu...>]

Dear list,

as you probably know, I'm the author of the reactive-banana package, 
which is a library for functional reactive programming (FRP) which can 
be used with wxHaskell. As such, I would like to propose a few changes 
to wxHaskell which are informed by FRP. Of course, while my primary aim 
is to gain better interoperability with my library, I think and hope 
that my proposed changes are of independent benefit.

Today, I would like discuss *composable events* and event handlers.


In wxHaskell, event handlers are currently set with the  on  combinator.

     set button [ on command := doSomething ]

Unfortunately, this approach has several problems that don't make it 
very composable:

1. Currently, setting an event handler will also *remove* any previous 
event handler.
2. The event handler may have have several curried parameters, or even none.


I have found that the most composable approach to events is the 
following type

     type Event a = AddHandler a
     newtype AddHandler a = AddHandler { addHandler :: (a -> IO ()) -> 
IO (IO ()) }

Example usage

     doSometing :: () -> IO ()
     ...
     removeSomething <- addHandler (on command button) doSomething

The idea is that  Event a  represents an event that carries data of type 
  a . If the event does not carry any data, then  a = () . The 
addHandler  function registers an additional event handler with the 
event, while keeping the old handlers intact. The return value of 
addHandler  can be used to remove the event handler again if desired. 
(This is how GTK does it, by the way.)

With this type, we can easily define new events from old ones, for instance

     instance Functor AddHandler where
         fmap f e = AddHandler $ \g -> addHandler e (g . f)

     filterJust :: AddHandler (Maybe a) -> AddHandler a
     filterJust e = AddHandler $ \g -> addHandler e (maybe (return ()) g)

     -- mouse click event
     click :: AddHandler Point
     click = filterJust . fmap matchClick $ mouse
         where
         matchClick (MouseLeftDown pt _) = Just pt
         matchClick _                    = Nothing

Note that this only works well if the event data always given as a 
single type, not multiple curried arguments.

I think this is very pleasant. In particular, it cleans up the confusion 
about the current crop of write-only events like  click  and  motion . 
It also looks a bit like FRP, though it is not powerful emough to become 
"true" FRP for reasons I don't want to go into right now.


The main drawback of the  AddHandler  approach is that we cannot keep 
the current syntax

   set button [ on click := .. ]

since setting an event handler rightfully implies that the old event 
handlers are removed. I'm somewhat undecided about possible solutions, 
but we could introduce a new assignment symbol

   set button [ on click :+ .. ]

that only works on events.


What do you think?


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com

Re: [wxhaskell-devel] Grief in building wxHaskell - a constructive approach

[Eric K. <eri...@gm...>]

On 24 Apr 2012, at 09:34, Andrew Butterfield wrote:
> What I am suggesting is that I help to develop those instructions by
> (1) cleaning up the dross leftover from previous attempts
> (2) Following them carefully (keeping a diary)
>    and adding feedback on the instructions to the wiki (using the Discussion facility)
> (3) Updating the wiki once some consensus on revised instructions have been reached

You get an enthusiastic +1 from me

I find it tricky to be systematic about it, especially given the diversity of possible platforms (combinatorial fun!), and the fact that targets move. I've been trying to move the pages towards something which explicitly accounts for this (eg. the “known configurations” tables, the timestamping).

One minor change lately, simpler URLs:

* http://www.haskell.org/haskellwiki/WxHaskell/Mac
* http://www.haskell.org/haskellwiki/WxHaskell/Linux
* http://www.haskell.org/haskellwiki/WxHaskell/Windows

Another thing which I think would help is just improving the visual appearance, not for the sake of making it nicer, but just using better markup to help separate bits of the pages from each other.

Good luck,

-- 
Eric Kow <http://erickow.com>