🚀 go-pugleaf

In article <212@dayton.UUCP> bill@dayton.UUCP (William T. Argyros) writes:
>I have played with the strange screen moving/pointer-hot-spot-changing
>also.  What happens is this:
> You can move the window down away from the Screen Bar (If you have not
>modified your source at all, it already starts 3 pixels down...). Now you
>can grap the Screen Bar and move it down.  When you move the screen back
>up again, there is a point, as you all know, when the screen stops moving
>up because it is at the top (makes sense, no?).  If you continue to move
>the mouse up at this point, the pointer will move, ON the Screen Bar.
>When this happens, the "Hot Point" of the pointer remains stationary, and
>the immage of the pointer moves up in relation to it.  You can "undo" this
>effect by again moving the screen down, then up again, stopping your mouse
>travel at the exact pixel that puts the screen at the very top.  Move any
>farther up, and you re-create the problem.  As of yet I have no idea why
>this happens, does anyone else?

My 2.1 never does that. Then again, I got rid of the screwy
screen/window lengths and positions before I ever turned it on. Since
Dave is doing oddness with sizes (longer than legal windows starting
at the bottom of the screen, etc), that it behaves in odd ways is not
surprising. The fixes are in init.c, and vt100.h for completeness.
I'll post them if I get sufficient requests.

Meanwhile, I'd like to know why Dave does things that way. Is there a
reason that I can't see?

Finally, I've also got changes (again, to 2.1 - any posted versions
will be to 2.2) to allow a custom screen to be opened using the colors
from the workbench. Since it didn't appear that these got into 2.2,
I'll probably mail to Dave and any one else that asks.

	<mike