event/away? stays false when mouse exit face whil LMB is down

[luce80]

event/away? stays false when mouse exit face whil LMB is down

[qtxie]

@luce80 Checking event/offset in the over event is a better option. You can know which edge the mouse cursor is on by checking event/offset and how far away from the edge.

[hiiamboris]

Your test doesn't show it, but I now think what happens is face gets locked to enable dragging. So away? gets generated once LMB is up. So this is more a question of naming, we think of away? as geometric property, but it's more complex. And whether away? should be applied to the last event with LMB down, or like now - only after its release. And of how do we control the locking? Does OS even allow us or we have to check the offsets?

[qtxie]

Your test doesn't show it, but I now think what happens is face gets locked to enable dragging. So away? gets generated once LMB is up. So this is more a question of naming, we think of away? as geometric property, but it's more complex. And whether away? should be applied to the last event with LMB down, or like now - only after its release. And of how do we control the locking? Does OS even allow us or we have to check the offsets?

We need a new option to control the locking.

[qtxie]

Expected behavior
Even if LMB is down event/away? should return true when the mouse cursor exits the face boundaries.

@luce80 What's the use case for this?

[luce80]

I am trying to implement an area using rich-text. When I start selecting the text and then , while still selecting, I exit the boundaries I expect the text to scroll to be able to continue selecting (like you can do in this same GitHub editor...). To do this it would be nice if event/away? still works even when LMB is down.
P.S. my example shows that if you click on the gray base and then try to "drag" it, when you exit it event/away? remains false.

[luce80]

Ok, never mind, the fix was quite easy:

away?: func [face event][event/offset <> min max 0x0 event/offset face/size]

I spent more time writing in this issue.