Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Hi, A few years ago I created this topic: https://plugincafe.maxon.net/topic/9969/13422_detect-leaving-userarea related to detecting the mouse leaving a GeUserArea. Andreas brought up the perfect solution of using RemoveLastCursorInfo and a callback. I have been using this solution ever since.
GeUserArea
RemoveLastCursorInfo
However, recently I have been looking into the ActivateFading and have discovered that while both functions work correctly on their own, as soon as you use both the RemoveLastCursorInfo's callback is never called.
ActivateFading
I do have a workaround for detecting leaving the userarea, using the BFM_FADE as described in the linked topic, but as mentioned it isn't without flaws. With that said, I just wanted to bring up the issue / limitation regarding using ActivateFading and RemoveLastCursorInfo together.
hi,
ActivateFading is also using RemoveLastCursorInfo internally. The last to be called should win.
Cheers, Manuel
@m_magalhaes said in GeUserArea - RemoveLastCursorInfo not compatible with ActivateFading:
ActivateFading is also using RemoveLastCursorInfo internally.
I more or less assumed this was the case. As such I went with an alternative solution using RemoveLastCursorInfo to be able to detect the mouse leaving the GeUserArea, while providing an own implementation for fading in and out.
Thanks for confirming.