From: Daan L. <daa...@xs...> - 2004-03-29 09:15:04
|
On Thu, 25 Mar 2004 17:42:41 +0000, Ian Lynagh <ig...@ea...> wrote: > Oh, I forgot to add that I could eliminate the flicker with > fullRepaintOnResize but then I can cause the screen to be redrawn > incorrectly as follows: Hmm, this doesn't happen on windows... I'll try it on wxGTK 2.5.1 to see what happens. > Hmm, but this only lets you specify globally whether you want to use > OpenGL, right? What I'd want to be able to do is install a single copy > of wxHaskell and use it to make either non-OpenGL or OpenGL programs. > Currently if I have the ability to make OpenGL programs then any > non-OpenGL programs I create will need to be linked against the GL > libraries anyway. Perhaps wxHaskell should create a libwxc-gl-0.6.so too > which contains the code for the OpenGL wxHaskell functionality to solve > this? In the same way that we have libwx_gtk-2.4.so.0 and > libwx_gtk_gl-2.4.so.0. I never thought about this. In the case of shared libraries, you are definitely right and we should generate two versions. However, I can now (in cvs head) link with static wxWidgets libraries, so I think that I can always support openGL in wxHaskell (as libwx_gtk_gl.a is linked in statically) -- the only question that remains is whether the application will load the system openGL libraries on demand or requires them to be present? (in the latter case, we need to provide two versions too). I am not to eager to provide two different versions of wxHaskell, so we should test first whether static linkage will work for us. Thanks for mentioning this, All the best, Daan. |