fc4373c7f623d72bd92fc560a157aa4b5c21ef43 |
|
17-Feb-2017 |
Scott Main <smain@google.com> |
Mark @ symbols in code snippet as literal so javadoc doesn't choke on them. Which for some reason only starts to happen when we start processing the annotation methods in this CL: https://googleplex-android-review.git.corp.google.com/#/c/1892771/ Change-Id: Ie933cc25b01d07cd04074aff6ca41e21803f73c5
/frameworks/base/core/java/android/view/ViewDebug.java
|
67e2ae86396c6d0f989285275cbf908dee5e71f7 |
|
12-Oct-2016 |
Aurimas Liutikas <aurimas@google.com> |
Fix import statement in view|transition|animation packages. This change also remove trailing whitespace. Test: code still compiles Change-Id: I7eff4546320d67d2bae58d31bad0625ea0791b8f
/frameworks/base/core/java/android/view/ViewDebug.java
|
4d052b3b5114703db75325100c4321914dccb219 |
|
15-Sep-2016 |
Manu Cornet <manucornet@google.com> |
Include window location after encoded view hierarchy Change-Id: I4e60e354dc56742bbd7dd52eb2191659d3453b29
/frameworks/base/core/java/android/view/ViewDebug.java
|
514c5ef8d5774d8820ed1bf90fe53af1606cf106 |
|
25-May-2016 |
Aurimas Liutikas <aurimas@google.com> |
Add missing @Deprecated annotations. Add missing @Deprecated annotations for methods with @deprecated tag in javadoc. Change-Id: I35b78ccb97832d86b914c21a300444ba29e33844
/frameworks/base/core/java/android/view/ViewDebug.java
|
8e89b31a62fb9ec5ad33908c5e8e9c7ab2fd949f |
|
10-Sep-2015 |
Chong Zhang <chz@google.com> |
Move window moving and resizing handling to WindowManager - add a startMoving API to initiate a window move from app, once the move starts WindowManager will take over the event handling. - detect touch events along window's outside border and start a resize if necessary Change-Id: Ic7e8baba34e0aa27a43173e044ffb46e93e219e0
/frameworks/base/core/java/android/view/ViewDebug.java
|
0d857b9028f2702ce439e13feccde8182d40e1e5 |
|
22-Apr-2015 |
Siva Velusamy <vsiva@google.com> |
Improve hierarchy viewer dump hierarchy latency Hierarchy Viewer obtains the properties for each view by using reflection and looking for fields and methods that have the @ExportedProperty annotation. Using reflection made it quite slow for large view hierarchies. This CL adds a new method (encode) to each class that wishes to export data to hiererachy viewer. Inside this method, the object can write a sequence of key, value pairs corresponding to the values it wants exported. With this change, the dump hierarchy operation that used to take more than 10 seconds can be performed in a few hundred milliseconds. Change-Id: I199ac2e7ca3c59ebcfec7e6bd201e134c41fd583
/frameworks/base/core/java/android/view/ViewDebug.java
|
a8a6516f62236a557669291602e6dcaa1a700531 |
|
17-Apr-2015 |
Mathieu Chartier <mathieuc@google.com> |
Update getExportedPropertyMethods to new reflection API Bug: 19264997 Change-Id: Ife79c469fdb09f30e3aefcfc3e0ce5ed32303fce
/frameworks/base/core/java/android/view/ViewDebug.java
|
3d529c5b0ae06953d4415aabcd7cf83333c3ef83 |
|
25-Mar-2015 |
Mathieu Chartier <mathieuc@google.com> |
Change getDeclaredFieldsUnchecked call to new return value Required for related libcore change. Bug: 19264997 Change-Id: I17ca0cf4b9ba853e59f4a6eff3a05d9d90cf23f9
/frameworks/base/core/java/android/view/ViewDebug.java
|
721fc2adf4d4d5b890b12cb2067db10e78888aba |
|
17-Oct-2014 |
Alan Viverette <alanv@google.com> |
Fix build Change-Id: Idd7ae84c0d128bd40f0e7a83882e4ed4181e8a4d
/frameworks/base/core/java/android/view/ViewDebug.java
|
99562fbbb40c72722468e5dc8c84b3e28494a20f |
|
14-Oct-2014 |
Alan Viverette <alanv@google.com> |
Check type resolution on declared methods and fields in ViewDebug BUG: 17375269 Change-Id: I8a74dfab1a1cf11b4240afb011d2729beea307c5
/frameworks/base/core/java/android/view/ViewDebug.java
|
7c744bdbf35aedbdde3a5ff9f2374e91f16f3641 |
|
10-Sep-2014 |
Jon Miranda <jonmiranda@google.com> |
Tries to resolve reference resource names instead of its data. Example: @16974751 can be resolved to android:style/TextApperance.Material. Bug: 17446752 Change-Id: I3ffede3ecc8689badd646a27d50a7a73ce45cf86
/frameworks/base/core/java/android/view/ViewDebug.java
|
042ad633bc68bdda2bb0c50216706d73575a5992 |
|
04-Sep-2014 |
Jon Miranda <jonmiranda@google.com> |
Added getStyleAttributes to access all Theme attributes. ViewDebug uses getStyleAttributes to get the attributes, and then gets the attribute name and value so that Hierarchy Viewer can display it. Bug: 17407087 Change-Id: I3577e32ae99668383701dc908bb46db14a75c3c4
/frameworks/base/core/java/android/view/ViewDebug.java
|
836c0a8b949d71293c996761691e065f0651acef |
|
11-Aug-2014 |
Jon Miranda <jonmiranda@google.com> |
Exposes style and theme data, adds developer option. Adds support for a String[] return type in ViewDebug; and in addition to that, the hasAdjacentMapping method can use the String array as means to map a key to its value. Adds DEBUG_VIEW_ATTRIBUTES to Settings so that the heavy per-view computations only affect those who opt in. This setting is used in CoreSettingsObserver to avoid impacting start time. Change-Id: I8f507e4e5361414c30d247e8d9815205feb5e91f
/frameworks/base/core/java/android/view/ViewDebug.java
|
48520210958b07d99791779abd52ba8034f3aa21 |
|
08-Aug-2014 |
Jon Miranda <jonmiranda@google.com> |
Changed flow in export methods to continue through the loop if it encounters an int[] return type. There are two such instances: 1. "private int[] mRules" within RelativeLayout LayoutParams. 2. "public int[] getLocationOnScreen" in View. When I added #2, we noticed missing annotated fields/methods in Hierarchy Viewer, but #1 also caused the same issue (mainly not exporting alignWithParent field) Bug: 16844914 Change-Id: I0d83a4391aa0565897cd7f0523995c97b7a4976d
/frameworks/base/core/java/android/view/ViewDebug.java
|
4597e9806948256e82b9f1cdaa7019cbbd912668 |
|
29-Jul-2014 |
Jon Miranda <jonmiranda@google.com> |
Exposed getLocationOnScreen, added formatToHexString method. In order to use the ExportedProperty annotation, I needed a public non-void method which is why I created a new "public int[] getLocationOnScreen()." The formatToHexString method is used to convert an int or byte to a hex string prefixed with "0x". I set the value to true on these flags: mGravity, mPrivateFlags, mSystemUiVisibility, mViewFlags, mGroupFlags, mMarginFlags, and flags. Change-Id: I5914992ba19b80643dfcc6caa487398452e18cbc
/frameworks/base/core/java/android/view/ViewDebug.java
|
68bf5bd3858684dbaa79f265943d7adaba982e85 |
|
06-Sep-2013 |
Chet Haase <chet@google.com> |
Show view overlays in hierarchyviewer ViewOverlays can hold Drawables and Views. But none of these things show up in hierarchyviewer, so what you see on the screen is not necessarily what you see in hierarchyviewer. This CL adds logic to ViewDebug to enable these views/drawables to be displayed. Issue #8943158 plumb overlay views through into hierarchy viewer Change-Id: I020e85530a68390b37986269fa3e9e7e43725bab
/frameworks/base/core/java/android/view/ViewDebug.java
|
97e8f6280484e3cde946b242982a0ddf95dae70e |
|
26-Apr-2013 |
Kristian Monsen <kristianm@google.com> |
Fix for bug 8623163: Call view methods on the UI thread Routing all methods invoked via reflection to the UI thread and waiting for the the return value. Change-Id: I8c38309253187f752b715453acb7f4f7bf54f9f8
/frameworks/base/core/java/android/view/ViewDebug.java
|
b365f91688dc081b3bcea82377ce0e94c09124ff |
|
28-Mar-2013 |
Fabrice Di Meglio <fdimeglio@google.com> |
Optimize ViewGroup.MarginLayoutParams memory and fix ViewDebug - use private flag bit field for ViewGroup.MarginLayoutParams - make ViewDebug support "byte" type for FlagMapping Change-Id: Iff7c31544e3ce2d29919c9424425f2bf87042b8b
/frameworks/base/core/java/android/view/ViewDebug.java
|
f9455fafb690f23cee9cc9a59bfb68f31e695990 |
|
18-Jan-2013 |
Siva Velusamy <vsiva@google.com> |
Support invoking view methods from hierarchy viewer This CL adds support for invoking any view method with primtive arguments, and setting layout parameters from the debugger (hierarchy viewer). requestLayout() and invalidate() are now just implemented using the more generic invokeMethod() command. Change-Id: Icffda251728a4963b35266786b0b6143bae7fe8e
/frameworks/base/core/java/android/view/ViewDebug.java
|
945bfb6068d4ac1414a37a3ebe4dc4d02383e38e |
|
07-Jan-2013 |
Siva Velusamy <vsiva@google.com> |
Support hierarchy viewer commands via DDM Hierarchy Viewer currently interfaces to the host via a socket opened by ViewServer which resides in the WindowManagerService. Since this has access to all windows, it is enabled only on debug builds. This CL adds necessary support to DDM to handle all the commands required for Hierarchy Viewer. It only misses two commands that are sent to the Window Manager (which we don't have access to from the applications). A future CL will remove the ViewServer functionality. Change-Id: I1dae316a00737b0cae4e640ccc97bf9bb1d05973
/frameworks/base/core/java/android/view/ViewDebug.java
|
dfab363807b3b44be4032e410f016e0a0d018426 |
|
03-Oct-2012 |
Romain Guy <romainguy@google.com> |
Fix rendering artifacts on tiled renderers Bug #7275145 This change fixes ViewRoot and adds extra debug information. It does not solve the problem entirely. Another CL will. Change-Id: I7e604ba38aad7f421769783dcbd998d6905ab2d9
/frameworks/base/core/java/android/view/ViewDebug.java
|
97723b2eb415d044d8dcee6a5ee3a2a3fb607b15 |
|
28-Sep-2012 |
Romain Guy <romainguy@google.com> |
Fix HierarchyViewer so it can load Contacts Change-Id: I5d5f400a9283f9c2431d91a10f85be42b02fe6a0
/frameworks/base/core/java/android/view/ViewDebug.java
|
4702a856973a553deb82f71b1d3b6c3db5dbf4ba |
|
18-Aug-2012 |
Dianne Hackborn <hackbod@google.com> |
More view hierarchy, fragment debugging. Add a View.toString() method. Rename all of the View private flags to have a PFLAG prefix to avoid going insane trying to figure out which constant goes with which flag. Activity.dump() now includes a summary of the activity's view hierarchy, using the View.toString() method. All exceptions thrown by FragmentManager now perform a dump of the owning activity state, where appropriate. Change-Id: I6482e397e10cb5a0612ab02ce6ed5131823437a6
/frameworks/base/core/java/android/view/ViewDebug.java
|
dde331cebd87982faded6818ad5f9927ff994c96 |
|
03-Aug-2012 |
Dianne Hackborn <hackbod@google.com> |
We can now (kind-of) change screen density on the fly. Preloaded drawables now have a density associated with them, so we can load the correct drawable if we are using a different density. Window manager now formally keeps track of the density for each screen, allowing it to be overridden like you can already do with size, and relies on this density to drive itself internally and the configurations it reports. There are a new set of Bitmap constructors where you provide a DisplayMetrics so they can be constructed with the correct density. (This will be for when you can have different windows in the same app running at different densities.) ActivityThread now watches for density changes, and pushes them to the DENSITY_DEVICE and Bitmap global density values for that process. A new am command allows you to change the density.
/frameworks/base/core/java/android/view/ViewDebug.java
|
f2361156c4aee3dad26f25c410fcf255656922d1 |
|
15-Jun-2012 |
John Reck <jreck@google.com> |
Fix doc link Change-Id: I5d2e6f04ed0ece6bf66b0b969c345108a1d372c5
/frameworks/base/core/java/android/view/ViewDebug.java
|
926cf56676d760579573470c7848dbf119a86779 |
|
14-Jun-2012 |
John Reck <jreck@google.com> |
Show WebView layers in hierarchyviewer Change-Id: I373e084d236baafe17982cfc367d167b81ca3e20
/frameworks/base/core/java/android/view/ViewDebug.java
|
e2d7f182ff2db26723089206c7d01f6695bd3dfc |
|
21-May-2012 |
Romain Guy <romainguy@google.com> |
Remove DEBUG_LATENCY flag This flag was replaced with the more versatile and powerful systrace. Change-Id: I2267698f86fe9ba9e1102856795ca641001fecd5
/frameworks/base/core/java/android/view/ViewDebug.java
|
13b907353f18215b52b5ceda24bbf520d91d72a1 |
|
21-May-2012 |
Romain Guy <romainguy@google.com> |
Remove unused, obsolete debug code All these features have either been abandonned and left un-maintained for years or can be replaced by systrace. Change-Id: I42e4579a8078744047e5fe08a7a15254970b09bc
/frameworks/base/core/java/android/view/ViewDebug.java
|
4213804541a8b05cd0587b138a2fd9a3b7fd9350 |
|
20-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility focus - framework Usefulness: Keep track of the current user location in the screen when traversing the it. Enabling structural and directional navigation over all elements on the screen. This enables blind users that know the application layout to efficiently locate desired elements as opposed to try touch exploring the region where the the element should be - very tedious. Rationale: There are two ways to implement accessibility focus One is to let accessibility services keep track of it since they have access to the screen content, and another to let the view hierarchy keep track of it. While the first approach would require almost no work on our part it poses several challenges which make it a sub-optimal choice. Having the accessibility focus in the accessibility service would require that service to scrape the window content every time it changes to sync the view tree state and the accessibility focus location. Pretty much the service will have to keep an off screen model of the screen content. This could be quite challenging to get right and would incur performance cost for the multiple IPCs to repeatedly fetch the screen content. Further, keeping virtual accessibility focus (i.e. in the service) would require sync of the input and accessibility focus. This could be challenging to implement right as well. Also, having an unlimited number of accessibility services we cannot guarantee that they will have a proper implementation, if any, to allow users to perform structural navigation of the screen content. Assuming two accessibility services implement structural navigation via accessibility focus, there is not guarantee that they will behave similarly by default, i.e. provide some standard way to navigate the screen content. Also feedback from experienced accessibility researchers, specifically T.V Raman, provides evidence that having virtual accessibility focus creates many issues and it is very hard to get right. Therefore, keeping accessibility focus in the system will avoid keeping an off-screen model in accessibility services, it will always be in sync with the state of the view hierarchy and the input focus. Also this will allow having a default behavior for traversing the screen via this accessibility focus that is consistent in all accessibility services. We provide accessibility services with APIs to override this behavior but all of them will perform screen traversal in a consistent way by default. Behavior: If accessibility is enabled the accessibility focus is the leading one and the input follows it. Putting accessibility focus on a view moves the input focus there. Clearing the accessibility focus of a view, clears the input focus of this view. If accessibility focus is on a view that cannot take input focus, then no other view should have input focus. In accessibility mode we initially give accessibility focus to the topmost view and no view has input focus. This ensures consistent behavior accross all apps. Note that accessibility focus can move hierarchically in the view tree and having it at the root is better than putting it where the input focus would be - at the first input focusable which could be at an arbitrary depth in the view tree. By default not all views are reported for accessibility, only the important ones. A view may be explicitly labeled as important or not for accessibility, or the system determines which one is such - default. Important views for accessibility are all views that are not dumb layout managers used only to arrange their chidren. Since the same content arrangement can be obtained via different combintation of layout managers, such managers cannot be used to reliably determine the application structure. For example, a user should see a list as a list view with several list items and each list item as a text view and a button as opposed to seeing all the layout managers used to arrange the list item's content. By default only important for accessibility views are regared for accessibility purposes. View not regarded for accessibility neither fire accessibility events, nor are reported being on the screen. An accessibility service may request the system to regard all views. If the target SDK of an accessibility services is less than JellyBean, then all views are regarded for accessibility. Note that an accessibility service that requires all view to be ragarded for accessibility may put accessibility focus on any view. Hence, it may implement any navigational paradigm if desired. Especially considering the fact that the system is detecting some standard gestures and delegates their processing to an accessibility service. The default implementation of an accessibility services performs the defualt navigation. bug:5932640 bug:5605641 Change-Id: Ieac461d480579d706a847b9325720cb254736ebe
/frameworks/base/core/java/android/view/ViewDebug.java
|
f76a50ce8fdc6aea22cabc77b2977a1a15a79630 |
|
09-Mar-2012 |
Ken Wakasa <kwakasa@google.com> |
Fix obvious typos under frameworks/base/core Change-Id: Ia5fc3db1bb51824e7523885553be926bcc42d736
/frameworks/base/core/java/android/view/ViewDebug.java
|
a175a5b7ea3682cb58cca7f9726d0b8171cd549d |
|
16-Feb-2012 |
Jeff Brown <jeffbrown@google.com> |
Encapsulate the ViewRootImpl's handler. This change makes it much easier to make sense of the messages that get posted to the ViewRootImpl's handler by encapsulating their point of dispatch within the ViewRootImpl itself. As part of this change, the View.AttachInfo now carries a reference to the ViewRootImpl itself, which simplifies some code that used to try to find the ViewRootImpl by getting the root view's parent. In principle, it might have been nice to hide the ViewRootImpl from the View hierarchy but in practice the two were coupled in many ways. Change-Id: I51ebccdf5f8c8c505cd6f17cdf594174d041dc54
/frameworks/base/core/java/android/view/ViewDebug.java
|
95db2b20d7bc0aaf00b1d4418124f5cf0a755d74 |
|
01-Dec-2011 |
Jeff Brown <jeffbrown@google.com> |
Improve latency instrumentation. Change-Id: I4edfa0a5659d207f7e46722e48ffa1dc43d2aa13
/frameworks/base/core/java/android/view/ViewDebug.java
|
6311d0a079702b29984c0d31937345be105e1a5e |
|
03-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Clear the bitmap from the canvas in a lot of places. Change-Id: I6b2071ac7b348c473b9bdd1b972d095aebbb4fb3
/frameworks/base/core/java/android/view/ViewDebug.java
|
65b345fa22b878e141b8fd8ece9c208df00fa40f |
|
28-Jul-2011 |
Romain Guy <romainguy@google.com> |
Reclaim more memory, more often. Yay. Change-Id: I04557ad575c307a55088549f48f0e9ad994b7275
/frameworks/base/core/java/android/view/ViewDebug.java
|
9a8c5cefcab3d5dec6ff63f0e99553e1aa9a4af8 |
|
22-Jul-2011 |
Romain Guy <romainguy@google.com> |
Ouput looper traces as traceview traces Change-Id: I96c8e85fd7497d970febbf6f5aefc4ab903add8e
/frameworks/base/core/java/android/view/ViewDebug.java
|
7eabe55db6b113f83c2cefcd06812648927de877 |
|
21-Jul-2011 |
Romain Guy <romainguy@google.com> |
Add looper profiling to adb shell am To profile the looper, run the following command: adb shell am profile looper start <process> <file> adb shell am profile looper stop <process> Change-Id: I781f156e473d7bdbb6d13aaffeeaae88bc01a69f
/frameworks/base/core/java/android/view/ViewDebug.java
|
648bee18a1ccd362445d562729250ff5910f16a0 |
|
21-Jul-2011 |
Romain Guy <romainguy@google.com> |
Convert looper traces to traceview traces Change-Id: If9238e8b00744118c1c4d2182727569f94deb638
/frameworks/base/core/java/android/view/ViewDebug.java
|
6dd005b48138708762bfade0081d031a2a4a3822 |
|
18-Jul-2011 |
Dianne Hackborn <hackbod@google.com> |
I. Can. Not. Stand. ViewAncestor. It was done so we would have the name "ViewRoot" available for a public API. However, the name "ViewAncestor" just makes no sense. So instead, change it to ViewRootImpl. Change-Id: If9599ca67896f339f6fefa7d1dde121201171d97
/frameworks/base/core/java/android/view/ViewDebug.java
|
f9284695e8c10dad4daf3d2c84f607483bcb56ca |
|
14-Jul-2011 |
Romain Guy <romainguy@google.com> |
Add new ViewDebug APIs to profile the event queue. Change-Id: I225bf288780b0244f459316e2765cfa29cd22c89
/frameworks/base/core/java/android/view/ViewDebug.java
|
1c90f032fad84b468fbe84d1faa11421e5209f89 |
|
24-May-2011 |
Romain Guy <romainguy@google.com> |
Code cleanup. Change-Id: I5469a2c826c054f20e045ea098bdbcad9e11b17b
/frameworks/base/core/java/android/view/ViewDebug.java
|
88b4f153e2be863d79f4d7f68af95e0f9375e4ec |
|
20-May-2011 |
Romain Guy <romainguy@google.com> |
Code cleanup. Change-Id: Ia6ea04b83832db2f39e3168ef2596c24273a7ef3
/frameworks/base/core/java/android/view/ViewDebug.java
|
ed30fd8e9a2d65ee5c8520de55b0089c219f390c |
|
23-Apr-2011 |
Chet Haase <chet@google.com> |
Add ability for hierarchyviewer to output displaylist info Clicking on a node in hierarchyviewer1 and hierarchyviewer2 and then clicking the new "Dump DisplayList" button will cause the display list for the selected node (including its children) to be output into logcat. Change-Id: Iad05f5f6cca0f8b465dccd962b501dc18fe6e053
/frameworks/base/core/java/android/view/ViewDebug.java
|
a17de9b493123f0d6e6d0b842150bf29322b7a88 |
|
05-May-2011 |
Chet Haase <chet@google.com> |
Revert "Add ability for hierarchyviewer to output displaylist info" This reverts commit b2a4b52e8d5e499d33e2765e8c47851bf0266299.
/frameworks/base/core/java/android/view/ViewDebug.java
|
42a3a39e231c02a3c2b7624cb7c64fe10d6ff4b0 |
|
05-May-2011 |
Chet Haase <chet@google.com> |
Merge "Add ability for hierarchyviewer to output displaylist info"
|
b2a4b52e8d5e499d33e2765e8c47851bf0266299 |
|
23-Apr-2011 |
Chet Haase <chet@google.com> |
Add ability for hierarchyviewer to output displaylist info Clicking on a node in hierarchyviewer1 and hierarchyviewer2 and then clicking the new "Dump DisplayList" button will cause the display list for the selected node (including its children) to be output into logcat. Change-Id: Id32f62569ad1ab4d533bc62987f3a7390c1bb4e6
/frameworks/base/core/java/android/view/ViewDebug.java
|
c6cc0f8c19d9eccf408a443fa2bf668af261dcd0 |
|
12-Apr-2011 |
Joe Onorato <joeo@google.com> |
Rename ViewRoot to ViewAncestor. ViewRoot is about to be a new public class for poking at ViewAncestor. Change-Id: Ie95d707c6d8bbb48f78d093d7b2667851812a7d5
/frameworks/base/core/java/android/view/ViewDebug.java
|
43a17654cf4bfe7f1ec22bd8b7b32daccdf27c09 |
|
07-Apr-2011 |
Joe Onorato <joeo@google.com> |
Remove the deprecated things from Config.java. These haven't been working since before 1.0. Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
/frameworks/base/core/java/android/view/ViewDebug.java
|
4e91a180be46c0c7c3bf398d4df4cbe2404216b5 |
|
07-Apr-2011 |
Jeff Brown <jeffbrown@google.com> |
Coalesce input events that arrive faster than 333Hz. Some drivers report individual finger updates one at a time instead of all at once. When 10 fingers are down, this can cause the framework to have to handle 10 times as many events each with 10 times as much data. Applications like PointerLocation would get significantly bogged down by all of the redundant samples. This change coalesces samples that are closely spaced in time, before they are dispatched, as part of the motion event batching protocol. Increased the size of the InputChannel shared memory buffer so that applications can catch up faster if they accumulate a backlog of samples. Added logging code to help measure input dispatch and drawing latency issues in the view hierarchy. See ViewDebug.DEBUG_LATENCY. Change-Id: Ia5898f781f19901d2225c529a910c32bdf4f504f
/frameworks/base/core/java/android/view/ViewDebug.java
|
daf98e941e140e8739458126640183b9f296a2ab |
|
10-Jan-2011 |
Chet Haase <chet@google.com> |
Use optimized display lists for all hwaccelerated rendering Previously, display lists were used only if hardware acceleration was enabled for an application (hardwareAccelerated=true) *and* if setDrawingCacheEnabled(true) was called. This change makes the framework use display lists for all views in an application if hardware acceleration is enabled. In addition, display list renderering has been optimized so that any view's recreation of its own display list (which is necessary whenever the visuals of that view change) will not cause any other display list in its parent hierarchy to change. Instead, when there are any visual changes in the hierarchy, only those views which need to have new display list content will recreate their display lists. This optimization works by caching display list references in each parent display list (so the container of some child will refer to its child's display list by a reference to the child's display list). Then when a view needs to recreate its display list, it will do so inside the same display list object. This will cause the content to get refreshed, but not the reference to that content. Then when the view hierarchy is redrawn, it will automatically pick up the new content from the old reference. This optimization will not necessarily improve performance when applications need to update the entire view hierarchy or redraw the entire screen, but it does show significant improvements when redrawing only a portion of the screen, especially when the regions that are not refreshed are complex and time- consuming to redraw. Change-Id: I68d21cac6a224a05703070ec85253220cb001eb4
/frameworks/base/core/java/android/view/ViewDebug.java
|
994ef9296a00523de1df424b4b760b4416ead58b |
|
13-Jan-2011 |
Christopher Tate <ctate@google.com> |
Turn off debugging logspam for release Fixes bug 2679101 Change-Id: I94cf1b1d0b732b2030008118eff3534f0e0608f7
/frameworks/base/core/java/android/view/ViewDebug.java
|
c21550a8d1dfc9e5359fe994cb48049a0bd4c82c |
|
06-Oct-2010 |
Brian Carlstrom <bdc@google.com> |
Adding android.os.Debug.countInstancesOfClass - Debug.countInstancesOfClass is just a wrapper on dalvik.system.VMDebug.countInstancesOfClass to avoid code from depending on the dalvik classes directly - Existing usages of VMDebug.countInstancesOfClass in ActivityThread and ViewDebug are converted to the new Debug.countInstancesOfClass - Existing use of OpenSSLSocketImpl.instanceCount, which is being removed, is converted to Debug.countInstancesOfClass(OpenSSLSocketImpl.class) Bug: 3015791 Change-Id: Iefa781292d5b82a63bad7254c913a09deb3b7888
/frameworks/base/core/java/android/view/ViewDebug.java
|
2c095f367779ef32130c72849936a2e3013c8492 |
|
04-Oct-2010 |
Christopher Tate <ctate@google.com> |
Refinements to drag/drop Thumbnail measurement & drawing has been moved out into a delegate class called View.DragThumbnailBuilder. This consolidates the thumbnail-related code as well as ensuring that the drag initiator does not have to know a priori where to place the thumbnail relative to the touch point *before* the thumbnail measurement step, as was previously the case. startDrag() no longer needs to be told where the current touch point is at the time the drag is launched. Drag events are now dispatched only to VISIBLE views. Dispatch shouldn't double-recycle events any more when the target window is local to the system process. Change-Id: I49419103765a0cad2e18ddfcdd6dacb94daf1ff1
/frameworks/base/core/java/android/view/ViewDebug.java
|
5429e1d1026db8922478b715672e6c0703bbf4a9 |
|
07-Sep-2010 |
Romain Guy <romainguy@google.com> |
Use static final debug fields. Change-Id: I304c39f54f609729bcec581091f285b2baa6fefa
/frameworks/base/core/java/android/view/ViewDebug.java
|
a14c8e0c67223fdc9a0746b370ae594a92530e78 |
|
04-Sep-2010 |
Romain Guy <romainguy@google.com> |
Bring back instances counts to dumpsys meminfo. Change-Id: Idd846e137e8e87cb93551ba13751df60a8046eed
/frameworks/base/core/java/android/view/ViewDebug.java
|
43b9b48f792e0b1b166af7f7fb6a32172e7f11c2 |
|
25-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Preventing the hierarchy viewer from getting stuck, once when trying to load the window data for SurfaceView and the Wallpaper, and in the case the captured node has disappeared. Change-Id: Iaff6bd501a2bb3faa7a394fff740479f6a95e899
/frameworks/base/core/java/android/view/ViewDebug.java
|
bef337f516eafaee8f3891e22688b74388570317 |
|
18-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Making sure the draw time is measured. Change-Id: I6bf8094aee03793f125008386c4fea730e95d07a
/frameworks/base/core/java/android/view/ViewDebug.java
|
91a7f5fef8a9fc496acef23f513cb48139e8dff5 |
|
11-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Making sure that the prefix is handled properly. Change-Id: Ic50327b1ed4d6b54753b5b3887508a53cd7a3497
/frameworks/base/core/java/android/view/ViewDebug.java
|
bea95162ca25bd00b0479d93739b6283795c3986 |
|
11-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Categorizing exported view properties. Change-Id: I79c42019836973d80662c21d195d088ae01537a0
/frameworks/base/core/java/android/view/ViewDebug.java
|
c6dc45700bf0c18708b0ad2f695ea85fadcbf131 |
|
07-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Make sure profiling is done only for views that are actually measured, laid out and drawn. Change-Id: I88c66e882be2781d079c51b6580a19c4e359c5b1
/frameworks/base/core/java/android/view/ViewDebug.java
|
f8e1219cf8992a22d6c48c2c70d4fbbccc2494f6 |
|
03-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Improving profiling of views. Change-Id: I1abb8c21f1769ad55416f37e7bfa1458b80ace63
/frameworks/base/core/java/android/view/ViewDebug.java
|
65554f27855ce1764123604b061b10346f8b8404 |
|
23-Mar-2010 |
Romain Guy <romainguy@android.com> |
Improve export to bitmap layers for HierarchyViewer. - Do not show layers with an invisible parent - Correctly draw extras from dispatchDraw() (ListView's dividers for instance) Change-Id: Id2e24ae9d52879290dffbf1cc446c5eda9522fbb
/frameworks/base/core/java/android/view/ViewDebug.java
|
1afd1c90ebe789b8d3a137004127a50d2db7e3b5 |
|
19-Mar-2010 |
Dianne Hackborn <hackbod@google.com> |
Maybe fix issue #2457218: Corrupt batterystats.bin file preventing phone boot - LIBtt68127 No steps to repro, but makes the code more robust by using the standard JournaledFile class and doing sanity checks on the input it reads. This required moving the JournaledFile class in to the framework (and we really should get rid of either it or AtomicFile, but they have different recovery semantics so that is tough). Also went through and cleaned up the file management in various places. Change-Id: Ieb7268d8435e77dff66b6e67bb63b62e5dea572e
/frameworks/base/core/java/android/view/ViewDebug.java
|
223ff5c0586adbbd1d6d57a3a4d176222e8b7434 |
|
03-Mar-2010 |
Romain Guy <romainguy@android.com> |
Add new CAPTURE_LAYERS command to HiearchyViewer protocol. This command is used by the desktop tool to export a given view hierarchy into a layered file format.
/frameworks/base/core/java/android/view/ViewDebug.java
|
cf635ae7c65de34f62a41cd330f25f4ee9ddc95b |
|
22-Jan-2010 |
Romain Guy <romainguy@android.com> |
Bring back buttons in dialogs. Bug #2390537
/frameworks/base/core/java/android/view/ViewDebug.java
|
38e951b62ed956501b11f0715e23e3bf70942f6d |
|
17-Dec-2009 |
Romain Guy <romainguy@android.com> |
Write HierarchyViewer's data in UTF-8. This change fixes issues with HierarchyViewer running on phones with a non en locale. The biggest problem occurred with spanish locales.
/frameworks/base/core/java/android/view/ViewDebug.java
|
236092a36216c79507ec19eb207831810caced19 |
|
15-Dec-2009 |
Romain Guy <romainguy@android.com> |
Fixes crash in HierarchyViewer when windows hash code exceed int capacity. Bug: 2321018
/frameworks/base/core/java/android/view/ViewDebug.java
|
237c1ceea36024cf4194212e713806e3ce8a1c49 |
|
08-Dec-2009 |
Romain Guy <romainguy@android.com> |
Improve exception message thrown when a View's state is of the wrong type.
/frameworks/base/core/java/android/view/ViewDebug.java
|
e551dc76bcde0e114b06e876eeb1d5f9d367fddf |
|
29-Jul-2009 |
Romain Guy <romainguy@android.com> |
Remove warning in non-eng builds.
/frameworks/base/core/java/android/view/ViewDebug.java
|
a1f3e4aef19882b4b81075d9205bd363efe1e66d |
|
05-Jun-2009 |
Romain Guy <romainguy@android.com> |
Fix int to string mapping of exported properties. The value generated by the mapping in a @ViewDebug.ExportedProperty annotation was always overriden by the resolveId attribute.
/frameworks/base/core/java/android/view/ViewDebug.java
|
5bcdff45bf4ada77ae7c95f520b795876adef75c |
|
15-May-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1846038. The dirty region can sometimes be modified by SurfaceFlinger. When this happens, force the view hierarchy to ignore the dirty flags.
/frameworks/base/core/java/android/view/ViewDebug.java
|
809a7f6080312f3e12f1a3a30eacf0e0c7627305 |
|
15-May-2009 |
Romain Guy <romainguy@android.com> |
New feature to track down #1846038. Adds the ability to export flags encoded in int values so as to make them human readable in HierarchyViewer.
/frameworks/base/core/java/android/view/ViewDebug.java
|
13922e03037d71a538f24ddf61c0b61bb4eb5af0 |
|
13-May-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1836075. Adds consistency checks for the View hierarchy. To enable them, you need a debug build and ViewDebug.sConsistencyCheckEnabled set to true in debug.prop. This change also lets you easily enable drawing and layout profiling in ViewRoot by setting ViewRoot.sProfileDrawing, ViewRoot.sProfileLayout and ViewRoot.sShowFps in debug.prop with a debug build.
/frameworks/base/core/java/android/view/ViewDebug.java
|
f8a7ceaef2e7d5cd530c9426bde91b6fa9a40b75 |
|
11-Apr-2009 |
Andy Stadler <> |
AI 145778: Manual merge changes 145382-145384 from cupcake. Automated import of CL 145778
/frameworks/base/core/java/android/view/ViewDebug.java
|
958b9adc086f126dcd757d29f0d7f443ae9064b2 |
|
01-Apr-2009 |
Dianne Hackborn <> |
AI 143899: am: CL 143896 Fix issue #1748954 and #1737952: #1748954 (New status bar fades into all white background): FrameLayout wasn't updating its foreground drawable when its padding changed, which would happen as the status bar is shown and hidden. To fix this I also ended up fixing a problem in the view debug stuff where we couldn't get a bitmap for a view that is the full screen size because it is too big... actually I just went ahead and added another function to snapshot the view hierarchy which works a lot better for us anyway. #1737952 (Home screen icons overlap with the notification bar after exiting any camera app): Originally I punted this because it only happened in rare situations, but now that home is always portrait it happens a lot more so it is more important to fix. This involved a few things to clean up hiding/showing the status bar: - We now determine when to hide and show it during layout, which allows us to do this at the time it is actually needed rather than during animation after we can actually catch it for the initial display of a window. This required tweaking the layout API so the policy can request a second layout pass if needed. - When doing layout, we are now much more aggressive about skipping the layout of windows. Basically anything that we know will be hidden in the near future is ignored for layout, so that it doesn't glitch as it is transfered out of the screen. The theory being that it is better to leave it as it was originally placed while we are transitioning it out, than to switch it to something slightly more correct. Original author: hackbod Merged from: //branches/cupcake/... Automated import of CL 143899
/frameworks/base/core/java/android/view/ViewDebug.java
|
105925376f8d0f6b318c9938c7b83ef7fef094da |
|
19-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake_rel/...@140373
/frameworks/base/core/java/android/view/ViewDebug.java
|
ba87e3e6c985e7175152993b5efcc7dd2f0e1c93 |
|
13-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake_rel/...@138607
/frameworks/base/core/java/android/view/ViewDebug.java
|
c39a6e0c51e182338deb8b63d07933b585134929 |
|
11-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@137873
/frameworks/base/core/java/android/view/ViewDebug.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/view/ViewDebug.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/view/ViewDebug.java
|
f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/frameworks/base/core/java/android/view/ViewDebug.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/view/ViewDebug.java
|