I previously posted this question on July 3 deep in an existing thread. I have not received an answer. I've been advised to start a new thread.
We have a case where View.getLocationOnScreen() seems to have a bug. The window where this happens is an EditTextPreference. To reproduce the problem: 1. bring up the AlarmClock app 2. click Menu 3. click Add Alarm 4. click Label 5. observe (either with HierarchyViewer or your eyes) the position of this window 6. click the "Alarm" EditText box 7. observe (eyes, HV) the new position of this window I have modified ViewDebug so it returns two more values for each view: the two values returned by View.getLocationOnScreen(). I named them screenX and screenY. HierarchyViewer (unchanged) displays these values. Before the window moves (step 5) I see these values from HierrarchyViewer: screenX: 27 screenY: 229 After the soft keyboard is displayed and the window is pushed up, (after step 6), I completely refresh the information in HierarchyViewer, these values have not changed. Since the window has definitely moved, I suspect this is a bug. Is there an alternative way using ViewDebug to getting the screen position of the EditText box under these circumstances? I'm stumped. -Sam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
