🚀 go-pugleaf

Bob Gonder <notbg@notmindspring.invalid> wrote:
>
>>If the mouse it at 100 and moved to 99, after that one pixel
>>move has been processed and the window is redrawn, the mouse
>>is now at 98 even though it wasn't moved!
>
> Which would indicate that you are reading client (box)
> coordinates at a time when you really want to know the real-
> world (screen) coordinates.

Using client relative v/s screen relative makes no difference
because the difference between the old position and the new
position is the same regardless of what variables are used to
calculate it.

Now, I do realize that in the above example, after the column
is resized, if I were to look at the mouse position in screen
relative terms, I wouldn't see that extra change but that's not
the problem. I used that example to illustrate that the scroll
position had changed which is the problem because it relocates
the header on screen. I can get the desired sizing effect but
it leaves the crHSplit mouse *way* out of position.

At the moment, I'm freezing the mouse at the screen relative
click point until the scroll position reaches zero and it works
but I don't like it.

~ JD