[orca/gnome-3-34] Use desktop coordinates instead of window coordinates for synthesized events



commit 6cf6df81d76516db5c6ef8d28ff9a562354dbcdf
Author: Joanmarie Diggs <jdiggs igalia com>
Date:   Fri Nov 15 10:53:37 2019 -0500

    Use desktop coordinates instead of window coordinates for synthesized events
    
    Theoretically it shouldn't matter as long as we're consistent. Mainly this
    should help with debugging as we're getting the pointer coordinates with
    respect to the full desktop.

 src/orca/eventsynthesizer.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/src/orca/eventsynthesizer.py b/src/orca/eventsynthesizer.py
index 31f92e226..1310107c0 100644
--- a/src/orca/eventsynthesizer.py
+++ b/src/orca/eventsynthesizer.py
@@ -222,12 +222,12 @@ def _scrollToLocation(obj, location, startOffset=None, endOffset=None):
         debug.println(debug.LEVEL_INFO, msg, True)
         return
 
-    before = component.getExtents(pyatspi.WINDOW_COORDS)
+    before = component.getExtents(pyatspi.DESKTOP_COORDS)
 
     if not _scrollSubstringToLocation(obj, location, startOffset, endOffset):
         _scrollObjectToLocation(obj, location)
 
-    after = component.getExtents(pyatspi.WINDOW_COORDS)
+    after = component.getExtents(pyatspi.DESKTOP_COORDS)
     msg = "EVENT SYNTHESIZER: Before scroll: %i,%i. After scroll: %i,%i." % \
           (before[0], before[1], after[0], after[1])
     debug.println(debug.LEVEL_INFO, msg, True)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]