Stephen James Hurd

documentation error

documentation error

Done, thanks for the report. It should be updated with the nightly build tonight.

Looks like at least parts of it are. The corpus is not... I've attached it here. Some of these are actually RIPv3 and some appear to be a combination of the two.

Mouse focus event tracking (DECSET/DECRST 1004)

I have a whole test setup I used for the RIPterm 1.54 work that runs RIPterm in DOSBox and a specially modified SyncTERM where the EGA aspect ratio isn't corrected (small change to conio/vidmodes.c) under X11. It connects both to a server that sends them RIP then captures screenshots using xwd and compares them. If they differ, it bisects the RIP file to find the broken code. It was still a nightmare to track down all the corner cases in fonts, buttons, and all the special rules about what exactly...

If a door does not steal the mouse, the mouse is for the user to use. It's an i-beam so the user can select text. If you hide the mouse, that would make it very difficult for the user to do what they want. The idea if my mouse pointer disappearing because I move it across a SyncTERM window sounds like something I would hate.

You seem to be conflating the window losing focus with the mouse leaving the window and the mouse leaving the pixel area of the window. Outside of fullscreen mode (and usually even in full-screen mode) there's a large area outside of the pixel coordinate system... black bars on the edges and "the rest of the desktop" all fall into this nebulous zone. Further, I can't think of any compelling reason a BBS needs to know if a specific window on my desktop has focus or not.