Kaiochao wrote:
Sorry, nope. In the webclient, yes. I thought so. =[ That's why I'm bumping this feature request. | |
The reason I'm mentioning the webclient is to maybe persuade you to switch over to that, since it's the client that's being worked on and will eventually make Dream Seeker obsolete. (Aside from bugs and performance issues, it's already way more capable than Dream Seeker ever could be.)
| |
Gonna give this one a powerful bump.
Lummox spitballed a framework for this, leveraging mouse macros: Add the following pseudo-wingets for each element: inner-mouse-pos outer-mouse-pos mouse-pos (inner for windows and panes, outer for everything else) these will return a text-coordinate of the mouse's current position in windows relative to the cursor. These can be passed along as an additional argument via embedded wingets or mouse macros. | |
I changed my mind and decided mouse-pos should just be the same as inner-mouse-pos for everything, on account of I'm sick of things having weird idiosyncratic behavior and this was a place I could choose to be more consistent.
| |
Lummox JR resolved issue with message:
New inner-mouse-pos and outer-mouse-pos params have been added to every control. There is also a mouse-pos param that's an alias for inner-mouse-pos. These are read-only, and represent the mouse coords relative to the upper left corner. Note that this will not be included when using * to read a control's parameters; the mouse-pos params must be explicitly read. | |
Login to reply.
You can track outside of dream seekers window?