|
From: Peter F. <pe...@si...> - 2023-01-13 13:12:20
|
On 13/01/2023 11:34, Carsten Haitzler wrote: [...] > as below - you want a larger thing that actually starts big and zooms > down to where the pointer is causing motion that your eyes follow to > that point and then can discover the mouse - there is no such feature > in e at this point. That is not a requirement. The requirement is for a BIG CURSOR. > if it's 2x as big it's still a pointer on a busy screen full of > content that if you don't have the visual acuity to make out is still > hard to see. If it's big and (eg) red it will be seen. > x cursors (libxcursor and x cursor themes) are "dumb" as i described. > simple images or a sequence of images to display. e renders its > cursor live from the same theme elements that make up everything else > (border, backgrounds, buttons, window borders) thus they can do > everything any theme element can do. it's all done the same way. thus > these objects accept signals (like a mouse click), scale like the > theme and size like all of these other theme elements - cursor is > defined in the theme like everything else. efl apps do the same as e > - they use efl to render the mouse cursor if they need a custom one > of their own. Ah. So I could write some code to make a bigger mouse pointer? > as a result x cursors are very limited in what they can do. a set of > N images for sizing and then N images in sequence looping if you > want animation and a hotspot. that's it. e's cursors can do this Except they cannot do sizing independently from the rest of the theme, if I understand you right. > any amount of signals can be sent to a pointer and the theme can > respond. I love your enthusiasm and explanation. Peter |