On Mon, 2005-05-09 at 23:07 +0000, Axel Simon wrote:
> +-- | Expose event delivering a 'Region'.
> +-- * Widgets that are very expensive to re-render, such as an image editor,
> +-- may prefer to use the 'onExposeRegion' call back which delivers a
> +-- 'Region' instead of a 'Rectangle'. A 'Region' consists of several
> +-- rectangles that need redrawing. The simpler 'onExpose' event encodes
> +-- the area to be redrawn as a bounding rectangle which might be easier
> +-- to deal with in a particular application.
> +onExposeRegion, afterExposeRegion ::
> + WidgetClass w => w -> (Region -> IO Bool) -> IO (ConnectId w)
> +onExposeRegion = connect_BOXED__BOOL "expose_event" marshExposeRegion False
> +afterExposeRegion = connect_BOXED__BOOL "expose_event" marshExposeRegion True
Yep, looks good to me. And my visualiser app works fine with it.
So, the PixBuf stuff next then? :-)
As I recall I was reasonably convinced that the solution I suggested
solves 4/5 of the problem with just one efficient primitive (or rather a
family of primitives, one for each useful colour depth, RGB8, RGBA8,
etc). Making Pixbuf an instance of MArray seems impossible to do sanely.
Is there a better alternative?
Get latest updates about Open Source Projects, Conferences and News.