from generating a huge whatis entry.

different from what was already there.

current canvas. This is useful to export dirty rectangles. Accordingly,
add caca_import_area_from_memory() and caca_import_area_from_file().

a more natural (x,y,w,h) 4-tuple to handle.

every frame, causing the mouse to flicker.

to keep source files under 1,000 lines of code.

their crap all over the place. There is still caca-sharp/obj
that it insists on creating (reported as Connect ID 301965).

we have dirty rectangles, fast autorepeat becomes perfectly usable.

as argument.

back to the libcucul merge.

currently dirty rectangles.

inner implementation still only handles one dirty rectangle, but this way
we can prepare supporting applictions for the future.

on Win64, including the .NET projects.

lesson to you: unit tests are good.

that anything outside the dirty rectangle is guaranteed to be unchanged, but
we currently mark far too many cells as dirty. This must be optimised.

Dirty rectangles are an upcoming optimisation that will tell the output
drivers which portion of the canvas has been really modified since the
last blit.

play with the Windows port, there is a 90-day evaluation version
available for free on the Microsoft website.

frame separator. Not extremely robust yet.

code for clarity.

Fixes ticket #51.