As long as there's a single binary (per release per platform) I'm for opengl
being part of it.
On Sat, Mar 29, 2008 at 6:56 AM, Eric Y. Kow <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Answering the one question I know an answer to.
>
> > In the meanwhile, I also found that the 0.10.3 binaries loose the
Hi,
The Microsoft Visual C++ 2005 SP1 Redistributable Package solves the
problem. Just great!
If anyone with access to wxHaskell webpage at sourceforge could add a note
in downloads page about this issue, could avoid others to have this problem.
Something like
You may need to install Microsoft V
Hi,
On Sat, 29 Mar 2008 23:29:08 +0900, Eric Y. Kow <[EMAIL PROTECTED]> wrote:
>> What's the EXWXEXPORT() macro for? It didn't seem very useful to me...
>
> (snip)
>
> I get the impression that it's there for some kind of portability reasons.
> Will need to do research on this mysterious __declspe
On Sat, 29 Mar 2008 22:41:19 +0900, Miguel Vilaça <[EMAIL PROTECTED]> wrote:
> Some pratical, to find a solutions is pointed in
> http://www.tech-archive.net/Archive/VC/microsoft.public.vc.mfc/2006-09/msg02020.html:
> "To see dependent DLLs, open your application with the dependency
> viewer (depen
Hi,
On Thu, 27 Mar 2008 07:55:50 +0900, José Miguel Vilaça <[EMAIL PROTECTED]>
wrote:
> I successfully installed Visual C++ 2005 Redistributable Package on Windows
> XP but the same error remains. I even rebooted (for some reason this usually
> solve many problems) the machine but no luck either.
Hi,
By the way, if I haven't already mentioned this, there is a wxhaskell-devel
that you may prefer to discuss this on. Personally, I'm happy either way.
> The code is so short that I embed it in this email. I'd be interested
> to hear any comments on the way I did this, and what you would want
Hi,
Answering the one question I know an answer to.
> In the meanwhile, I also found that the 0.10.3 binaries loose the
> opengl support compared with 0.9.4 as pointed in
> http://wxhaskell.sourceforge.net/download.html.
> Is there some reason for this?
There used to be a flag bug in wxWidge
Hi again,
After several unsuccesseful tries, and some googling, I found out many
complains of people seeing the message "The applicattion failed to
initialize properly (0xc0150002). Click OK to terminate the
application." when they run their executables out of the devellopment
machine.
So, I have successfully added some of the missing bindings that I needed.
The code is so short that I embed it in this email. I'd be interested
to hear any comments on the way I did this, and what you would want to
change before committing it to wxhaskell.
1) Loading images from in-memory blocks
