[wxhaskell-users] paintraw and setting layout

Hi,
Is it possible that the layout is a bit strange when you use the paintRaw
event in one panel.
When I use a glCanvas window (and set the paintRaw event) I'm unable to make
something like
layout := row 0
[ floatLeft $ widget glField
, floatRight $ widget anotherPanel]
Everyone expects that the "anotherPanel" appears on the right side of the
frame. What really happened is that the glField glCanvas window is drawn on
the left side of the frame and the anotherPanel (which only consists of a
single button) is placed in the left upper corner too.
The button is drawn over the glField.
Could it be that the paintRaw event influences the behavior of the layout?
Cheers
Patrick

Thread view

Hi,
Is it possible that the layout is a bit strange when you use the paintRaw
event in one panel.
When I use a glCanvas window (and set the paintRaw event) I'm unable to make
something like
layout := row 0
[ floatLeft $ widget glField
, floatRight $ widget anotherPanel]
Everyone expects that the "anotherPanel" appears on the right side of the
frame. What really happened is that the glField glCanvas window is drawn on
the left side of the frame and the anotherPanel (which only consists of a
single button) is placed in the left upper corner too.
The button is drawn over the glField.
Could it be that the paintRaw event influences the behavior of the layout?
Cheers
Patrick

Announcement: wxHaskell version 0.9
----------------------------------------------------------------------
<http://wxhaskell.sourceforge.net&gt;
I am pleased to announce a new release of wxHaskell.
This new release has support for the printing and much improved
support for processes and the grid control.
Binary installers are provided for MacOS X, Linux (RPM), and Windows,
for use with ghc 6.2.2.
Have fun,
Daan Leijen.
----------------------------------------------------------------------
wxHaskell is a portable GUI library for Haskell. The goal of the
project is to provide an industrial strength portable GUI library, but
without the burden of developing (and maintaining) one ourselves.
wxHaskell is therefore build on top of wxWidgets -- a comprehensive
C++ library that is portable across all major GUI platforms; including
GTK, Windows, X11, and MacOS X. Furthermore, it is a mature library
(in development since 1992) that supports a wide range of widgets with
native look-and-feel, and it has a very active community (ranked among
the top 25 most active projects on sourceforge).
Since most of the interface is automatically generated from the
wxEiffel binding, the current release of wxHaskell already supports
about 75% of the wxWindows functionality -- about 2900 methods in 500
classes with 1400 constant definitions.
wxHaskell has been build with GHC 6.x on Windows, MacOS X and
Unix systems with GTK. A binary distribution is available for Windows,
Linux (RPM) and MacOS X.
And even if you don't intend to write GUI's yourself, it will be fun
to check out the screenshots at <http://wxhaskell.sourceforge.net&gt;.
----------------------------------------------------------------------
Version 0.9
-------------
Non backward compatible changes:
- Changed "image" attribute to "picture"
Backward compatible additions:
- Added Multiple OpenGL Canvas example and fixed old example.
- Much improved process support in WXCore.Process. Use
"processExecAsyncTimed" instead of "processExecASync".
- Full printing support in WXCore.Print
- Added SpintControl events.
- Fixed bug in MultiListBoxes where selections would only be
added.
- Added "pixelBufferGetPixels" and "pixelBufferSetPixels" and
according functions for images.
- Added "image" and made it an instance of the "Sized" class
exported "imageCreateFromPixels" and "imageCreateFromPixelArray"
- Added "drawImage"
- Removed dependency on "readline" package in ghc 6.2.2
- Added "--cache" argument to configure script
Bug fixes:
- fixed "on command" event handlers in submenus.

On Wednesday 16 March 2005 12:14, Georg Martius wrote:
> Hi Ben,
>
> Sorry for the confusing discussion. As Daan said the dependency stuff
> was not that trivial to get. However, please find my patches for 0.8
> and 0.9 attached. To apply the patches please enter the wxHaskell-0.X
> source directory and run
>
> > patch configure < configure_0.X_ghc6.4.diff
> > patch makefile < makefile_0.X_ghc6.4.diff
> > patch makefile.lib < makefile.lib_0.X_ghc6.4.diff
Thanks a lot!
I'll try your patches. My current workaround is/was to disable
dependency generation, but this is of course not a sustainable
solution. BTW, I also had to write package description files in the new
format. Which ones do you use?
Some of the examples under directory 'contrib' are broken in version
0.9. I needed to make a number of (superficial) changes to get them to
compile and run. Interestingly, and this is something I often observed
with Haskell, as soon as I got it to compile, everything worked as
expected. The changes where easy to make, using the haddock generated
docs. WxHaskell is cool!
Ben