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: Jaap v. d. W. <ja...@wi...> - 2009-07-09 07:50:09
|
Windows experience with non-Ascii symbols: I tried to print the suits (\x03 through \x06) for a buttoned solitair game. It didn't work. They do appear on the teletype ghc console, but on the wx buttons only boring squares are printed. Did I compile wx Widgets ... I don't know, and I don't want to know. Jaap van der Woude On Wed, 2009-07-08 at 20:27 +0100, Eric Kow wrote: > On Wed, Jul 08, 2009 at 20:13:35 +0100, Eric wrote: > > I don't know - I'm using the binary that came with the Windows > > distribution... > > Hmm, I'm afraid I can't help much there. > > I imagine it's either an issue with the fonts or the distribution, > as I have the Unicode stuff working fine on my Linux box. > > I'll attach the code to UTF8Sampler if it helps (this is in the > darcs repository, but for some reason, it was omitted from the > distribution, probably an oversight). > > Maybe other Windows users have experience to comment? > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ wxhaskell-users mailing list wxh...@li... https://lists.sourceforge.net/lists/listinfo/wxhaskell-users -- Jaap van der Woude <ja...@wi...> |
From: Eric Y. K. <eri...@gm...> - 2009-07-08 21:23:08
|
On Wed, Jul 08, 2009 at 22:14:47 +0100, Eric wrote: > Thanks. I've run the UTF8Sampler - Some stuff appears but no Chinese, > Korean, Tibetan, Mongolian or Japanese characters. By any chance, could it just be a matter of fonts? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric <er...@ma...> - 2009-07-08 21:15:02
|
Eric Kow wrote: > On Wed, Jul 08, 2009 at 20:13:35 +0100, Eric wrote: > >> I don't know - I'm using the binary that came with the Windows >> distribution... >> > > Hmm, I'm afraid I can't help much there. > > I imagine it's either an issue with the fonts or the distribution, > as I have the Unicode stuff working fine on my Linux box. > > I'll attach the code to UTF8Sampler if it helps (this is in the > darcs repository, but for some reason, it was omitted from the > distribution, probably an oversight). > Thanks. I've run the UTF8Sampler - Some stuff appears but no Chinese, Korean, Tibetan, Mongolian or Japanese characters. |
From: Eric K. <eri...@gm...> - 2009-07-08 19:29:21
|
On Wed, Jul 08, 2009 at 20:27:30 +0100, Eric Kow wrote: > I'll attach the code to UTF8Sampler if it helps (this is in the > darcs repository, but for some reason, it was omitted from the > distribution, probably an oversight). Whoops, you'll want this file too -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric K. <eri...@gm...> - 2009-07-08 19:27:38
|
On Wed, Jul 08, 2009 at 20:13:35 +0100, Eric wrote: > I don't know - I'm using the binary that came with the Windows > distribution... Hmm, I'm afraid I can't help much there. I imagine it's either an issue with the fonts or the distribution, as I have the Unicode stuff working fine on my Linux box. I'll attach the code to UTF8Sampler if it helps (this is in the darcs repository, but for some reason, it was omitted from the distribution, probably an oversight). Maybe other Windows users have experience to comment? -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric K. <eri...@gm...> - 2009-07-08 19:26:53
|
On Wed, Jul 08, 2009 at 19:38:50 +0100, Eric wrote: > import Graphics.UI.WX > > main = start $ do > f <- frame [text := "Traqer"] > p <- panel f [] > t <- textCtrl p [text := "\x3008\x3009", clientSize := sz 300 300] > set f [layout := container p $ fill $ widget t, clientSize := sz 400 400] > return() Thanks for including a minimal example! When I run this, I see something that looks like open and close brackets, which I bet is what you were expecting. Is your wxWidgets compiled with --enable-unicode? Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Eric <er...@ma...> - 2009-07-08 19:13:49
|
Eric Kow wrote: > > Is your wxWidgets compiled with --enable-unicode? > I don't know - I'm using the binary that came with the Windows distribution... |
From: Eric <er...@ma...> - 2009-07-08 19:00:31
|
Dear all, I have written the following program: import Graphics.UI.WX main = start $ do f <- frame [text := "Traqer"] p <- panel f [] t <- textCtrl p [text := "\x3008\x3009", clientSize := sz 300 300] set f [layout := container p $ fill $ widget t, clientSize := sz 400 400] return() However a box appears instead of the unicode characters '\x3008' and '\x3009'. Does wxhaskell not support these unicode characters? |
From: Eric K. <eri...@gm...> - 2009-07-07 19:16:07
|
Hi, On Mon, Jul 06, 2009 at 16:08:04 +0900, Renick Bell wrote: > I'd like to try out wx. I'm trying to install wx through Cabal. > Perhaps I'm making a mistake without realizing it. If I'm reading it > correctly, Cabal says I'm missing stm-2.1.1.2, but ghc-pkg list says > that I have it. ??? I'm afraid I haven't looked too deeply into the details, but I'll say that the simplest method for now (as far as I know) is to install wxcore in the global package repository, as root. Once you've done that, you can just cabal install wx. This is a pretty big stumbling block. I really hope that in the future, the wxHaskell team will be able to improve on this. So far, my thinking is that it would be good to push the wxC bits into a separate project, making it a nice clean external dependency. The idea being that the user would have to install wxc herself, but that having done so, would be able to just cabal install. But these things take time :-) Thanks, -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Renick B. <re...@gm...> - 2009-07-06 07:08:09
|
I'd like to try out wx. I'm trying to install wx through Cabal. Perhaps I'm making a mistake without realizing it. If I'm reading it correctly, Cabal says I'm missing stm-2.1.1.2, but ghc-pkg list says that I have it. ??? ...[snip]... install: /home/renick/.cabal/lib/wxcore.pkg cat config/wxcore.pkg | sed -e "s|\${wxhlibdir}|/home/renick/.cabal/lib|" | ghc-pkg update - Reading package info from stdin ... done. wxcore-0.11.1.2: dependency stm-2.1.1.2 doesn't exist (use --force to override) make: *** [wxcore-register] Error 1 cabal: Error: some packages failed to install: wx-0.11.1.2 depends on wxcore-0.11.1.2 which failed to install. wxcore-0.11.1.2 failed during the final install step. The exception was: exit: ExitFailure 2 $ ghc-pkg list ...[snip]... regex-compat-0.92, regex-posix-0.94.1, stm-2.1.1.2, ...[snip]... -- Renick Bell http://the3rd2nd.com |
From: anty <ma...@an...> - 2009-07-03 16:10:34
|
Hi, I've discovered that taskBarIconDelete crashes when you use it twice. I first encountered this on Windows when I used it in the "on close" attribute for removing the icon when I close the program. I then tried to reproduce this on Linux and it first seemed to be a Windows-only problem. But when I removed the "propagateEvent" on Linux I couldn't close my program the first time, only the icon was deleted. The second time I tried to close the program it segfaulted. I first thought it correlated with the use of evtHandlerOnTaskBarIconEvent, because removing this seemed to fix everything. (maybe this is an uncorrelated, second, bug?) But then I thought by myself: It doesn't make sense that the program crashes on Linux on the second close attempt. So wrote a minimal example to try out what happens when I delete the taskbar-icon more than one time. And it segfaulted, like I expected. On both, Linux and Windows. When I delete in once, I can close my application afterwards successfully. When I delete it twice, it segfaults. Here are the environments I tested my program in: * Windows XP using GHC 6.10.3 with wx-0.11.1.2 with wxWidgets-2.8.10 * Ubuntu 9.04 using GHC 6.10.3 with wx-0.11.1.2 with wxWidgets-2.8.9.1 This is the minimal example I've created to reproduce the bug, I also attached it along with an icon: module Main where import Graphics.UI.WXCore import Graphics.UI.WX main :: IO () main = start example example :: IO () example = do icon <- iconCreateFromFile "example.ico" (sz 16 16) tbicon <- taskBarIconCreate f <- frame [] b <- button f [text := "delete taskbar icon", on command := taskBarIconDelete tbicon] taskBarIconSetIcon tbicon icon "example" set f [layout := container f $ row 0 [widget b]] |
From: Claus R. <cla...@ta...> - 2009-07-01 14:24:25
|
> Eric elided some of the MSDN links I dug up when first asking my > question, see > > http://www.mail-archive.com/wxh...@li.../msg00629.html oh, the wonders of automated software - you need to remove the alphanumerical garbage that the mailinglist software inserted into my post, presumably to protect what looked like an email address.. Claus |
From: Claus R. <cla...@ta...> - 2009-07-01 13:26:35
|
> I agree with Claus that there is a potential problem here, although it > is perhaps overstated slightly. However, as someone who works at a > company which is very careful about IP issues, I understand the point. For all I know, the license note for the vcredist_x86.exe redistributable package could be an error on the Microsoft site - it doesn't appear (at least not in such a prominent place) for earlier versions, and why would they want to keep customers of their VS developers from using the C++ runtime libraries required? But if you want to rely on that, you'd need to ask MS for clarification. After all, it is not just a question for wxhaskell developers, but for the users of the applications they develop, right? If only VS users have the right to redistribute the runtime libs, and they fail to do so when building the binaries, then noone down the line can use these binaries. Eric elided some of the MSDN links I dug up when first asking my question, see http://www.mail-archive.com/wxh...@li.../msg00629.html I'm not an MS developer, but it seems to me that it should be possible simply to include the dlls in question with the wxhaskell binary, without changing whatever build process you've set up, and without running into license issues. In fact, the deployment examples explicitly discuss redistribution of VC90.CRT, as an alternative to relying on vcredist_x86.exe. As for cygwin/mingw builds: the instructions state that they need an *older* make than the one required for ghc builds, which makes me reluctant to try myself. Given how often this has popped up even before the license note was added, it would seem important to solve this at the source, once and for all. Anyway, good to see that wxhaskell has not gone dead again. Claus > There are a couple of approaches we could take. > > One is to build wxWidgets as a completely static library, and statically > link with wxC. If we do this, we could continue to deliver binaries > built using the Microsoft toolchain, although wxHaskell binaries would > then be enormous (and I should note that Microsoft now goes to some > trouble to make it tedious to statically link the run-time). > > I think, therefore, that the best approach is probably to deliver our > Windows binary builds based on the MinGW toolset. I've never actually > used this on Windows (I'm very familiar with the GNU toolset on Linux > and other unices), and I suspect that this may be the case for the other > developers. This means a transition for me, which I'm quite happy to > make in theory, but which will probably take some time for to complete > in practice. > > A handy benefit of using MinGW is that we would no longer suffer from > 'Manifest hell' - the exciting new scenario Microsoft has produced to > replace DLL hell... > > One thing to note is that I would like to be very certain that any > change to the binary distribution model does not introduce a dependency > on cygwin.dll for wxHaskell applications on Windows, since this would > effectively require all apps based on our binaries to be GPL licensed, > which I find unacceptable. > > Regards > Jeremy > > Eric Kow wrote: >> Hi Shelarcy, >> >> Is this something you know what to do with? Perhaps the non-VS build >> should be the default? >> >> Thanks! >> >> On Mon, Jun 29, 2009 at 09:35:33 +0100, Claus Reinke wrote: >> >>> "Claus Reinke" <cla...@ta...> wrote in message >>> news:h103ak$aep$1...@ge...... >>> >>>> I tried updating some old wxHaskell code to work with recent >>>> ghc/wxHaskell. On a windows xp system, I have installed the >>>> ghc-6.10.3 and wxhaskell-bin-msw2.8.10-ghc6.10.3-0.11.1.2-0 >>>> binary installers. After compiling my code, I can't run the executables, >>>> due to missing dependencies (copied from event viewer): >>>> >>>> Dependent Assembly Microsoft.VC90.CRT could not be found >>>> and Last Error was The referenced assembly is not installed on your system. >>>> >> >> ... >> >> >>>> This has come up before, and the advice has been to install extra bits >>>> of Visual Studio. However, the latest recommended version of these >>>> files clearly states that they may only be used with a valid Visual Studio >>>> license: >>>> >> >> >>>> http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en >>>> >>>> So that is a no-go. As I understand the VS deployment models, VS >>>> distinguishes between components that may be redistributed and those >>>> that may not. wxHaskell should only depend on the former, and should >>>> include them in the binary installer, because the kind person building >>>> wxHaskell via VS is the only one who can include those redistributable >>>> dependencies. >>>> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> wxhaskell-users mailing list >> wxh...@li... >> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users >> > > > ------------------------------------------------------------------------------ |
From: Jeremy O'D. <jer...@gm...> - 2009-07-01 11:52:44
|
Hi all, Very busy with work, so this will need to be a short answer. I agree with Claus that there is a potential problem here, although it is perhaps overstated slightly. However, as someone who works at a company which is very careful about IP issues, I understand the point. There are a couple of approaches we could take. One is to build wxWidgets as a completely static library, and statically link with wxC. If we do this, we could continue to deliver binaries built using the Microsoft toolchain, although wxHaskell binaries would then be enormous (and I should note that Microsoft now goes to some trouble to make it tedious to statically link the run-time). I think, therefore, that the best approach is probably to deliver our Windows binary builds based on the MinGW toolset. I've never actually used this on Windows (I'm very familiar with the GNU toolset on Linux and other unices), and I suspect that this may be the case for the other developers. This means a transition for me, which I'm quite happy to make in theory, but which will probably take some time for to complete in practice. A handy benefit of using MinGW is that we would no longer suffer from 'Manifest hell' - the exciting new scenario Microsoft has produced to replace DLL hell... One thing to note is that I would like to be very certain that any change to the binary distribution model does not introduce a dependency on cygwin.dll for wxHaskell applications on Windows, since this would effectively require all apps based on our binaries to be GPL licensed, which I find unacceptable. Regards Jeremy Eric Kow wrote: > Hi Shelarcy, > > Is this something you know what to do with? Perhaps the non-VS build > should be the default? > > Thanks! > > On Mon, Jun 29, 2009 at 09:35:33 +0100, Claus Reinke wrote: > >> "Claus Reinke" <cla...@ta...> wrote in message >> news:h103ak$aep$1...@ge...... >> >>> I tried updating some old wxHaskell code to work with recent >>> ghc/wxHaskell. On a windows xp system, I have installed the >>> ghc-6.10.3 and wxhaskell-bin-msw2.8.10-ghc6.10.3-0.11.1.2-0 >>> binary installers. After compiling my code, I can't run the executables, >>> due to missing dependencies (copied from event viewer): >>> >>> Dependent Assembly Microsoft.VC90.CRT could not be found >>> and Last Error was The referenced assembly is not installed on your system. >>> > > ... > > >>> This has come up before, and the advice has been to install extra bits >>> of Visual Studio. However, the latest recommended version of these >>> files clearly states that they may only be used with a valid Visual Studio >>> license: >>> > > >>> http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en >>> >>> So that is a no-go. As I understand the VS deployment models, VS >>> distinguishes between components that may be redistributed and those >>> that may not. wxHaskell should only depend on the former, and should >>> include them in the binary installer, because the kind person building >>> wxHaskell via VS is the only one who can include those redistributable >>> dependencies. >>> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > _______________________________________________ > wxhaskell-users mailing list > wxh...@li... > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users > |
From: Eric K. <eri...@gm...> - 2009-06-29 18:09:09
|
Hi Shelarcy, Is this something you know what to do with? Perhaps the non-VS build should be the default? Thanks! On Mon, Jun 29, 2009 at 09:35:33 +0100, Claus Reinke wrote: > "Claus Reinke" <cla...@ta...> wrote in message > news:h103ak$aep$1...@ge...... > >I tried updating some old wxHaskell code to work with recent > > ghc/wxHaskell. On a windows xp system, I have installed the > > ghc-6.10.3 and wxhaskell-bin-msw2.8.10-ghc6.10.3-0.11.1.2-0 > > binary installers. After compiling my code, I can't run the executables, > > due to missing dependencies (copied from event viewer): > > > > Dependent Assembly Microsoft.VC90.CRT could not be found > > and Last Error was The referenced assembly is not installed on your system. ... > > This has come up before, and the advice has been to install extra bits > > of Visual Studio. However, the latest recommended version of these > > files clearly states that they may only be used with a valid Visual Studio > > license: > > http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en > > > > So that is a no-go. As I understand the VS deployment models, VS > > distinguishes between components that may be redistributed and those > > that may not. wxHaskell should only depend on the former, and should > > include them in the binary installer, because the kind person building > > wxHaskell via VS is the only one who can include those redistributable > > dependencies. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Claus R. <cla...@ta...> - 2009-06-29 08:35:58
|
No solution, no workaround, not even a reply? Claus "Claus Reinke" <cla...@ta...> wrote in message news:h103ak$aep$1...@ge...... >I tried updating some old wxHaskell code to work with recent > ghc/wxHaskell. On a windows xp system, I have installed the > ghc-6.10.3 and wxhaskell-bin-msw2.8.10-ghc6.10.3-0.11.1.2-0 > binary installers. After compiling my code, I can't run the executables, > due to missing dependencies (copied from event viewer): > > Dependent Assembly Microsoft.VC90.CRT could not be found > and Last Error was The referenced assembly is not installed on your system. > > Resolve Partial Assembly failed for Microsoft.VC90.CRT. Reference > error message: The referenced assembly is not installed on your system. > > Generate Activation Context failed for C:\WINDOWS\system32\wxc-msw2.8.10-0.11.1.2.dll. > Reference error message: The operation completed successfully. > > Application popup: NetEdit.exe - Application Error : The application failed > to initialize properly (0xc0150002). Click on OK to terminate the application. > > This has come up before, and the advice has been to install extra bits > of Visual Studio. However, the latest recommended version of these > files clearly states that they may only be used with a valid Visual Studio > license: > > http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en > > So that is a no-go. As I understand the VS deployment models, VS > distinguishes between components that may be redistributed and those > that may not. wxHaskell should only depend on the former, and should > include them in the binary installer, because the kind person building > wxHaskell via VS is the only one who can include those redistributable > dependencies. > > Deployment (C++) > http://msdn.microsoft.com/en-us/library/zebw5zk9.aspx > > Redistributing Visual C++ Files > http://msdn.microsoft.com/en-us/library/ms235299.aspx > > Deployment Examples > http://msdn.microsoft.com/en-us/library/ms235285.aspx > > (the examples explicitly mention wxHaskell's missing library, so it > seems to be among the redistributable ones) > > Unless I am misunderstanding the process or licensing terms, the > wxHaskell installer should provide the missing component, or > non-VS users will not be able to use the wxHaskell binary. > > Claus > > > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects |
From: Claus R. <cla...@ta...> - 2009-06-13 11:45:06
|
I tried updating some old wxHaskell code to work with recent ghc/wxHaskell. On a windows xp system, I have installed the ghc-6.10.3 and wxhaskell-bin-msw2.8.10-ghc6.10.3-0.11.1.2-0 binary installers. After compiling my code, I can't run the executables, due to missing dependencies (copied from event viewer): Dependent Assembly Microsoft.VC90.CRT could not be found and Last Error was The referenced assembly is not installed on your system. Resolve Partial Assembly failed for Microsoft.VC90.CRT. Reference error message: The referenced assembly is not installed on your system. Generate Activation Context failed for C:\WINDOWS\system32\wxc-msw2.8.10-0.11.1.2.dll. Reference error message: The operation completed successfully. Application popup: NetEdit.exe - Application Error : The application failed to initialize properly (0xc0150002). Click on OK to terminate the application. This has come up before, and the advice has been to install extra bits of Visual Studio. However, the latest recommended version of these files clearly states that they may only be used with a valid Visual Studio license: http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en So that is a no-go. As I understand the VS deployment models, VS distinguishes between components that may be redistributed and those that may not. wxHaskell should only depend on the former, and should include them in the binary installer, because the kind person building wxHaskell via VS is the only one who can include those redistributable dependencies. Deployment (C++) http://msdn.microsoft.com/en-us/library/zebw5zk9.aspx Redistributing Visual C++ Files http://msdn.microsoft.com/en-us/library/ms235299.aspx Deployment Examples http://msdn.microsoft.com/en-us/library/ms235285.aspx (the examples explicitly mention wxHaskell's missing library, so it seems to be among the redistributable ones) Unless I am misunderstanding the process or licensing terms, the wxHaskell installer should provide the missing component, or non-VS users will not be able to use the wxHaskell binary. Claus |
From: Andrew U. F. <fr...@ge...> - 2009-06-11 07:56:55
|
a possible workaround is to temporarily set the event handler to 'return ()' dox2 bEn w = do putStrLn "dox2 start" i <- get w selection p <- get bEn (on select) set bEn [on select := return ()] set bEn [items := ["xx"]] set bEn [on select := p] putStrLn $ "selection " ++ show i putStrLn "dox2 end" |
From: Andrew U. F. <fr...@ge...> - 2009-06-11 07:45:09
|
i encounter a problem possibly related to a problem reported earlier by Mads in 2007 (segmentation fault): when i change the list box items within the event handler, the event handler is called immediately (i.e. inside itself, recursively). it seems that the event is still active in the queue at this moment; i think it should be cleared upon entry (not on exit) of the event handler. any comments? what is the best work-around? andrew the following program demonstrates the error: module Main where -- OnCommandTest where {- test for on command jumping too often -} import Graphics.UI.WX main = start $ do w <- frame [text := "test on command event processing"] f <- panel w [] listVar <- varCreate (["aa"]:: [String]) doButton <- button f [text := "do"] quitButton <- button f [text := "Quit", on command := close w] aEn <- textEntry f [text := "aEn"] bEn <- singleListBox f [items := ["123456789012345678901234567890"] ] set aEn [on enterKey := dox bEn listVar] set bEn [on select ::= dox2 bEn] set doButton [on command := dox bEn listVar] let lay = fill $ column 5 [ row 5 [label "buttons" , widget doButton , widget quitButton ] , row 5 [label "text entry", hfill $ widget aEn] , hfill $ widget bEn ] set w [ layout := minsize (sz 300 300) $ container f lay ] return () dox bEn listVar = do putStrLn "dox start" l <- varGet listVar let l2 = l ++ ["bb"] set bEn [items := l2] varSet listVar l2 repaint bEn putStrLn "dox end" dox2 bEn w = do putStrLn "dox2 start" i <- get w selection set bEn [items := ["xx"]] putStrLn $ "selection " ++ show i putStrLn "dox2 end" |
From: anty <ma...@an...> - 2009-06-09 12:06:42
|
Hi all, I'm trying to find a way to construct a list that includes checkboxes with text next to them. It should pretty much look like the following: http://www.simpol.com/guiimages/wxchecklist.jpg I guess this is possible with the Style-parameter of "listCtrlEx"? I couldn't find any tutorials or sample code, so if you could point me in the right direction, I would really appreciate it! Thanks! |
From: Günther S. <gue...@we...> - 2009-06-04 17:20:09
|
Hi all, can I embed icons, or rather bitmaps into the executable? Do I need to adjust the code that I developed, using runghc mostly, just before compilation, ie. creating the .exe? Günther |
From: Rolf H. <rol...@st...> - 2009-05-27 18:02:01
|
Hi Henk-Jan, Thanks for the hint! I was able to figure out what the problem was and could solve it. For people how want to know: The nil in the "set f" function was not allowed. Using IO and GUI in the same do-expression is actually not a problem. Regards, Rolf On 25.05.2009, at 22:17, Henk-Jan van Tuyl wrote: > On Sun, 24 May 2009 10:33:13 +0200, Rolf Haynberg <rol...@st... > > wrote: > >> Hello wxhaskell users, >> >> I'm new to wxhaskell and I can't solve the following problem on my >> own >> (tried to find a solution online for hours). >> >> What I'm trying to do is simple: I want to display the time from now >> until a time in the future. For which I read the current time with >> getClockTime, do some calculations and then paint the time. The >> following compiles but quits immediately when I run the app (no >> error). >> >> ... >> demo :: IO () >> demo = do f <- frameFixed [text := "Countdown"] >> currenttime <- getClockTime >> p <- panel f [on paint := (writeTimeDiff >> currenttime) ] >> set f [layout := fill $ container p $ margin 10 $ column 5 >> []] >> >> writeTimeDiff :: ClockTime -> DC a -> Rect -> IO () >> writeTimeDiff currenttime dc _ = drawText dc (getTimeDiff >> currenttime) >> (Point 2 2) [] >> >> getTimeDiff :: ClockTime -> String >> getTimeDiff = calendarTimeToString . toUTCTime . >> timeDiffToClockTime . >> (diffClockTimes eta) >> where eta = toClockTime (CalendarTime 2010 January 1 16 45 0 0 >> Thursday 0 "CEST" 0 False) >> ... >> >> Don't worry about how I calculate the time difference. Imho the >> problem has something to do with >> currenttime <- getClockTime >> >> I hope anyone sees a problem in the code. I have the feeling that I'm >> missing something fundamental here. >> >> Thanks in advance, >> Rolf >> > > Use the GHCi debugger [1] to see where the crash occurs. > > > > [1] http://www.haskell.org/ghc/docs/latest/html/users_guide/ghci-debugger.html > > > -- > Regards, > Henk-Jan van Tuyl > > > -- > http://functor.bamikanarie.com > http://Van.Tuyl.eu/ > -- > > |
From: Henk-Jan v. T. <hj...@ch...> - 2009-05-25 23:20:10
|
On Sun, 24 May 2009 10:33:13 +0200, Rolf Haynberg <rol...@st...> wrote: > Hello wxhaskell users, > > I'm new to wxhaskell and I can't solve the following problem on my own > (tried to find a solution online for hours). > > What I'm trying to do is simple: I want to display the time from now > until a time in the future. For which I read the current time with > getClockTime, do some calculations and then paint the time. The > following compiles but quits immediately when I run the app (no error). > > ... > demo :: IO () > demo = do f <- frameFixed [text := "Countdown"] > currenttime <- getClockTime > p <- panel f [on paint := (writeTimeDiff > currenttime) ] > set f [layout := fill $ container p $ margin 10 $ column 5 > []] > > writeTimeDiff :: ClockTime -> DC a -> Rect -> IO () > writeTimeDiff currenttime dc _ = drawText dc (getTimeDiff currenttime) > (Point 2 2) [] > > getTimeDiff :: ClockTime -> String > getTimeDiff = calendarTimeToString . toUTCTime . timeDiffToClockTime . > (diffClockTimes eta) > where eta = toClockTime (CalendarTime 2010 January 1 16 45 0 0 > Thursday 0 "CEST" 0 False) > ... > > Don't worry about how I calculate the time difference. Imho the > problem has something to do with > currenttime <- getClockTime > > I hope anyone sees a problem in the code. I have the feeling that I'm > missing something fundamental here. > > Thanks in advance, > Rolf > Use the GHCi debugger [1] to see where the crash occurs. [1] http://www.haskell.org/ghc/docs/latest/html/users_guide/ghci-debugger.html -- Regards, Henk-Jan van Tuyl -- http://functor.bamikanarie.com http://Van.Tuyl.eu/ -- |
From: Rolf H. <rol...@st...> - 2009-05-24 08:46:01
|
Hello wxhaskell users, I'm new to wxhaskell and I can't solve the following problem on my own (tried to find a solution online for hours). What I'm trying to do is simple: I want to display the time from now until a time in the future. For which I read the current time with getClockTime, do some calculations and then paint the time. The following compiles but quits immediately when I run the app (no error). ... demo :: IO () demo = do f <- frameFixed [text := "Countdown"] currenttime <- getClockTime p <- panel f [on paint := (writeTimeDiff currenttime) ] set f [layout := fill $ container p $ margin 10 $ column 5 []] writeTimeDiff :: ClockTime -> DC a -> Rect -> IO () writeTimeDiff currenttime dc _ = drawText dc (getTimeDiff currenttime) (Point 2 2) [] getTimeDiff :: ClockTime -> String getTimeDiff = calendarTimeToString . toUTCTime . timeDiffToClockTime . (diffClockTimes eta) where eta = toClockTime (CalendarTime 2010 January 1 16 45 0 0 Thursday 0 "CEST" 0 False) ... Don't worry about how I calculate the time difference. Imho the problem has something to do with currenttime <- getClockTime I hope anyone sees a problem in the code. I have the feeling that I'm missing something fundamental here. Thanks in advance, Rolf |
From: luiz d. <lui...@ya...> - 2009-05-16 02:35:11
|
I got the following error when upload a file. Xrc Examples of repository gives the same error ... Loading package wxcore-0.11.0 ... linking ... done. Loading package wx-0.11.0 ... linking ... done. <interactive >: user error (wxHaskell: NULL object: xmlResoucerLoadFrame) <interactive>: interrupted <interactive>: warning: too many hs_exit()s Then the program crash Doing without. XRC interfaces operate normally help me Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com |