>With your screen code, are you planning on any overlay capabilities
>like the clock hack in 1.03, or is it full screen only?
>Being able to say "Box with the text "Blah" at coord "2,34"
>for 2 seconds would be awesome.

Cool. I'm planning on it NOW!

How about a simple ioctl() (from userland) for "HIJACK_SET_GEOM" to specify a "window" geometry (upper left coordinate, height, and width)?

This would be somewhat messy to implement internally, but doable.

Method (1) would be to modify the blatter routine to only blat the rectangle we specify. But given the extreme weirdness in the hardware displaybuf layout, this likely ain't gonna happen.

Method (2) might be simpler: merge the player's displaybuf with our rectangle before blatting. A lessor known "secret" of the hijack method is that the player continues to update the "screen" even while we are running -- except its updates never make it to the blatter.

The second Method looks a lot less efficient than the first, but might not be too bad because its simpler logic makes for faster code than Method 1.. mmm..

Cheers