#MOUSE WARP OPENGL FULL#
#MOUSE WARP OPENGL SOFTWARE#
#MOUSE WARP OPENGL WINDOWS#

Your display footprint in this image buffer at full resolution may be smaller than the footprint of the cursor pointer on your display. In another implemented use case of XWarpPointer(), your Display hosts a reduced resolution view of a giga-pixel (or larger) image buffer and this view is used to navigate within the buffer. So you have hundreds of functions accessible with a single mouse click and moving the cursor through a logical tree, that may select other logical trees to overlay itself to arbitrary depth.ДЄbsence of capability to warp the pointer makes all this impossible, and you are stuck with a stovepipe interface. It becomes a 3-Dimensional logical network of functionality. If you release R mouse anywhere else the menu simply disappears.ДЄny active function may create its own menu using the same gui builder and scheme. If you release R mouse at the end of a logical tree, the selected function executes. As you move through a menu with R mouse depressed, new menus pop up at the cursor position in a menu.

#MOUSE WARP OPENGL SOFTWARE#

Since the software is user extensible with an internal gui builder, you slide the cursor down the menu to 'Extensions' among the other options.ДЄ user extension menu then overlays the core menu, and the cursor position snaps to the origin of the Extensions menu.ДЄll menus are logical trees. Every pixel on the screen is data.ДЄ tabular pop-up menu appears out of nowhere with its origin at the cursor position. Just data and an ancillary window displaying statistics, histograms, in realtime with the moving cursor, if enabled. You are in a hi-res screen field of image data from a buffer that may be gigapixels. Discarding core capabilities requires deeper thought than I am seeing. The argument that this capability is 'unneeded' is hugely presumptive and forces development into yet another conceptual stovepipe.ДЇor some of us, LINUX is about total developmental freedom in an open conceptual space, not about moving everything into conceptual stovepipes. And some of us use this capability and have designed around it.

#MOUSE WARP OPENGL WINDOWS#

Yes that gives Apple reliability and rigid control over the user experience, but it is not the only path to reliability.ДЄpplication control of the cursor across open windows in a networked environment is probably a step too far, but to be able to move the cursor under application control within the bounds of the window of current focus does not seem an insurmountable effort, since it has been in place for 30 years. Apple stovepipes solutions into channels. This is what is being done, and I do not see the need for it beyond the desire to 'look and feel' like another platform with a totally different user philosophy than LINUX.

It makes no sense to remove functionality that is of continuing relevance when its removal cancels an entire domain of possible GUI design and user interactivity. The issue is whether core Xlib functionality should be discarded in the process. Of course Xlib needs to be replaced, and Wayland is the replacement. The issue is not whether Xlib should be replaced to address updated Display technology and network protocols.

Mouse warp opengl