On 19/01/15 07:24 PM, Bill Spitzak wrote:
This seems excessively complicated compared to a version that just
figures out an x/y pair to use instead of seat-pointer-x/y and leaves
the rest of the code alone.
It's also more complicated than a patch that just removes the keybind
for zoom in/zoom
This seems excessively complicated compared to a version that just
figures out an x/y pair to use instead of seat-pointer-x/y and leaves
the rest of the code alone.
On 01/09/2015 10:45 AM, Derek Foreman wrote:
Any time the zoom is updated the best zoom target will be calculated
with the
Any time the zoom is updated the best zoom target will be calculated
with the following priority:
1) The current pointer location.
2) The last known location of the pointer that initiated the zoom.
3) The center of the current keyboard focus. If the focus is split across
heads, multiple heads
