cached pinboard layout?
Unable to parse email body. Email id is 9588
Unable to parse email body. Email id is 9588
Nick Levine <ndl@ravenbrook.com> writes:
> I have a capi:pinboard-layout on which there might sometimes be
> thousands of objects (typically a fuzz of short lines). Expose events
> take too long, because everything gets redrawn every time. I'd like to
> cache the bits.
>
> In the past, with pure capi:output-panes, I've dealt with this
> successfully by creating a pixmap port, doing all my drawing to that,
> and bitblting from pixmap to output-pane in the latter's
> display-callback.
>
> Has anyone ever done anything remotely like this for a
> pinboard-layout?
I'm looking for tips on how to do this too. On Mac OS X, LW seems to
use some Cocoa built-in buffering, so it's not a problem, but on
Windows and X11 I also sometimes have problems with redraws that
are too cpu-intensive.
--
regards,
Espen Vestre
Netfonds Bank ASA
I have a capi:pinboard-layout on which there might sometimes bethousands of objects (typically a fuzz of short lines). Expose eventstake too long, because everything gets redrawn every time. I'd like tocache the bits.In the past, with pure capi:output-panes, I've dealt with thissuccessfully by creating a pixmap port, doing all my drawing to that,and bitblting from pixmap to output-pane in the latter'sdisplay-callback.Has anyone ever done anything remotely like this for apinboard-layout?Thanks,- nick
Chris Melen <relativeflux@hotmail.co.uk> writes: > There is also the :draw-pinboard-objects :buffer (or :local-buffer) > option with a pinboard-layout. This involves a backing pixmap (or > one per object if you specify :local-buffer). I use this to avoid > flicker on XP. It's easier than doing buffering yourself, but in my > experience somewhat slower - in fact I am in the process of moving > back to doing my own buffering. I've tried :buffer on XP, but drawing gets painfully slow. -- (espen)