d98dcab679ce477c3acba298feb8fc2302e69333 |
|
02-May-2016 |
Jaewan Kim <jaewan@google.com> |
Fix crash when device doesn't support picture-in-picture Bug: 28512987 Change-Id: Ic8287d70fed491d7493d443ba7d9633b7d9aaea9
/frameworks/base/core/java/android/view/Window.java
|
f0fd218382b96f052d22a2e8ee00510cc23a6d1e |
|
20-Apr-2016 |
Jaewan Kim <jaewan@google.com> |
PIP: Send KEYCODE_WINDOW to app first if PIP isn't exist Bug: 27954955 Change-Id: I517e378d5c1672ac0eb87bdf4375b7d733276e58
/frameworks/base/core/java/android/view/Window.java
|
82ee6753305b484d778743882fb827c6b73d82c1 |
|
22-Apr-2016 |
Andres Morales <anmorales@google.com> |
Merge "FrameMetricsListener API council changes" into nyc-dev
|
d908c6294dc23b71575f74d4b49d2aacd982a427 |
|
20-Apr-2016 |
Andres Morales <anmorales@google.com> |
FrameMetricsListener API council changes Bug: 28296251 Change-Id: I8fe0d8b37c0a3220666570f242f9c20fa16b78ab
/frameworks/base/core/java/android/view/Window.java
|
37696cccd8925ca6e4aa6f2ca6f29807066c7f1e |
|
21-Apr-2016 |
Rob Carr <racarr@google.com> |
Merge "Respect manually set HARDWARE_ACCELERATED flag." into nyc-dev
|
13678ee74e7a2234d82d8383fa08cab9e87dcfa7 |
|
20-Apr-2016 |
Robert Carr <racarr@google.com> |
Respect manually set HARDWARE_ACCELERATED flag. When choosing what window parameters to pass on to child windows, we need to respect the manually set FLAG_HARDWARE_ACCELERATED from Window.setFlags() in addition to the activity manifest value, and the value from setWindowManager. Given that we pass the value on to child windows from when setWindowManager is called, I think it makes sense to pass it when setFlags is called. Bug: 27099358 Bug: 23036374 Change-Id: Ie018841aadd270910fe0f8bc5a5ddca3bfbee69b
/frameworks/base/core/java/android/view/Window.java
|
43e38de2530fecbbdea81c52d0fde90333432356 |
|
15-Apr-2016 |
Ruchi Kandoi <kandoiruchi@google.com> |
window: Adds a Sustained Performance Mode window flag. Adds setSustainedPerformanceMode(boolean) API for applications to set the mode for a given window. The mode will be disabled automatically when the window is no longer in focus. Bug: 28150358 Change-Id: Ibe8bc564eeaaccbcaad5c4f792cda16da931dffd Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
/frameworks/base/core/java/android/view/Window.java
|
933076d80561751618f462b26309ce9e4c3ff3bf |
|
30-Mar-2016 |
Andrii Kulian <akulian@google.com> |
Refactor usages of Picture In Picture and Multi Window (1/4) Bug: 27365860 Change-Id: I1590e430a12ceb84cb83da295e0bf7e4378fea96
/frameworks/base/core/java/android/view/Window.java
|
fcd7e80b21cc9db6be00e37371401ea1d0938796 |
|
10-Mar-2016 |
Clara Bayarri <clarabayarri@google.com> |
Keyboard Shortcuts: plumb deviceId through Bug: 27673736 Change-Id: Ie72807aa8c2bfd142b081a6a915e101c16d31473
/frameworks/base/core/java/android/view/Window.java
|
2a6d9aa1cdfc7489fdc9ef1a0cec51c6c3c29c7d |
|
17-Mar-2016 |
Sunny Goyal <sunnygoyal@google.com> |
Adding a default implementation for the new Window.Callback method Bug: 27702972 Change-Id: I6b8c1766ecf871801006d4dc47796a819e49bb57
/frameworks/base/core/java/android/view/Window.java
|
910beb8f5d9042163e2ad0dbb744d9f147db9604 |
|
03-Feb-2016 |
Andres Morales <anmorales@google.com> |
updates to FrameStatsObserver API - Rename to FrameMetrics to avoid collision with existing android.view.FrameStats class - Make FrameMetricsObserver implementation detail, exposing FrameMetricsListener interface as public API and wrapping in FrameStatsObserver to maintain state - Remove dropped frame count call, in favor of passing as parameter to callback method. - Move away from raw timestamp access in favor of Metric IDs which represent higher-level, more stable stages in a frame lifecycle and match the categories exposed in the onscreen bars. - Support many-to-many Window<->FrameMetricsListener relationship Change-Id: I00e741d664d4c868b1b6d0131a23f8316bd8c5c2
/frameworks/base/core/java/android/view/Window.java
|
f6f5f4ed94d1c98322fc370d4a79b9e6d576eaee |
|
01-Feb-2016 |
Wale Ogunwale <ogunwale@google.com> |
Merge "Made some changes to window caption APIs"
|
3b93a4d351aeb154fba8a4b2fa66ca25a951993d |
|
30-Jan-2016 |
Wale Ogunwale <ogunwale@google.com> |
Renamed Activity class multi-window APIs As requested by API council. Bug: 26507736 Change-Id: I2a87c5eb3c1b48d52703103c2a4f72c250a9a827
/frameworks/base/core/java/android/view/Window.java
|
a504ca398874321d636ccac1a914d19ae3fd843b |
|
31-Jan-2016 |
Wale Ogunwale <ogunwale@google.com> |
Made some changes to window caption APIs As recommended by API council. Bug: 26509365 Change-Id: I4efca89e2e14ffcf66ab8372f694e8bbf58d6fef
/frameworks/base/core/java/android/view/Window.java
|
06f5bc70a667a02b14e31d3f53f91d3661e30666 |
|
16-Dec-2015 |
Andres Morales <anmorales@google.com> |
expose hwui frame stats through FrameStatsObserver Change-Id: I88884bafc8e2f6d7f67a36d3609490e83cf8afd5
/frameworks/base/core/java/android/view/Window.java
|
4846ee3cc378001128680f2a3309c7e60bfcac75 |
|
07-Jan-2016 |
Jorim Jaggi <jjaggi@google.com> |
Optimize window relayouts when dragging divider - Communicate the resize mode to ViewRootImpl. If it is a docked divider resize, do not call relayout for every traversal. - Do not call Task.resizeWindows() unconditionally when changing Stack bounds. It might be just a move. - However, not calling relayout breaks layout bounds while relaunching. To fix that, do the following: -- Inform ViewRootImpl that the activity just relaunched, and force a relayout call in the next traversal so the client can pick up the unfrozen bounds. -- When unfreezing the bounds, cause a traversal in window manager. Bug: 25015474 Change-Id: Iab9a445dabce4f6ec1e25957038fe40a4be65246
/frameworks/base/core/java/android/view/Window.java
|
75e097965cc273d33192555b0e65de3dbc1753ce |
|
29-Jul-2015 |
Clara Bayarri <clarabayarri@google.com> |
Request Keyboard Shortcuts for SysUI Dialog via Window Keyboard shortcuts are requested via WindowManager, and the request pipes through to the view root and the window callback. Bug: 22405482 Change-Id: Ic0071e91c7b554be3ac9df71e9539ee8a60e822e
/frameworks/base/core/java/android/view/Window.java
|
411c06fbf9040f20778de1ae612e6ab5d6a5a3d4 |
|
07-Jan-2016 |
Filip Gruszczynski <gruszczy@google.com> |
Only allow activities to move to full screen stack. We allowed activities to move to any stack, but that's too much freedom. Instead we only allow them to move from freeform stack to a fullscreen stack. Change-Id: I04de9bbf18cf4431d7bd34d6c727de82802661ef
/frameworks/base/core/java/android/view/Window.java
|
eb6722c0bc87dd5419df1eb92268b824c2d29b50 |
|
08-Dec-2015 |
Wale Ogunwale <ogunwale@google.com> |
Fixed bug with caption not showing for some apps that handle config changes We currently decide when to show the decor caption onConfigurationChanged However, if the app handles configuration changes or the threshold isn't big enough for the configuration change to be reported to the app, we don't display the caption in some cases when transitioning from fullscreen mode to freeform mode. We now also use the onMultiWindowModeChanged call to also determine if the caption should be visible. Change-Id: I237437f04ad90f904912ebac0253245f547b0e3e
/frameworks/base/core/java/android/view/Window.java
|
3dec081967db3c0e906ff272d632618e260b6413 |
|
09-Dec-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Remaining APIs for freeform window caption. The APIs are: * setting a listener for the area of the caption where we display control buttons; this is intended for apps that overlay the caption on their content, so they don't display the content in that area and clash with the buttons; * specifying the color pallete of controls in the caption; by default we try to infer the best color from the theme (dark buttons for light theme and vice versa), but in case we get it wrong, we allow the developer to overwrite it; * specifying the caption background during the resizing; by default we try to infer a good color from the theme, but in case we do it wrong, we allow the developer to overwrite this. The CL also includes merging of layouts decor_caption_dark and decor_caption_light into a single one. Not only it reduces code duplication, but also is necessary for allowing adjustment of the controls color pallete after the layout was created. Bug: 25486369 Bug: 25818398 Change-Id: Ib87fe849b07df341893ec7873982bf7ab932f6d5
/frameworks/base/core/java/android/view/Window.java
|
9b81e406b03f9a1c39e33e54919d7bd84ce8998d |
|
09-Dec-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Remove Window.setDecorView API. We currently don't have a strong use case for this. Change-Id: I106aaf1224d7934964d9b92628fd3cdd42507c46
/frameworks/base/core/java/android/view/Window.java
|
63250651ca4656fc1b9e9ffb9c48d481df80454d |
|
18-Nov-2015 |
Filip Gruszczynski <gruszczy@google.com> |
API for overlaying app content over decor caption in freeform windows. Bug: 25486369 Change-Id: I8fba30dd690d9f0ccc48149f57ce254286b0c2ae
/frameworks/base/core/java/android/view/Window.java
|
02a5a6bb9ba05bdf7517de90ede49fb535ea06ca |
|
02-Nov-2015 |
Wale Ogunwale <ogunwale@google.com> |
Merge "Added StackId object for checking what features a stack supports"
|
3797c22ea16e932329ebffdc7e7ce09f9ecd9545 |
|
27-Oct-2015 |
Wale Ogunwale <ogunwale@google.com> |
Added StackId object for checking what features a stack supports Helps make the code easier to follow since we are no longer checking multiple stack ids at various decision points. Bug: 25282299 Change-Id: Ifa6864a1ef56ce2eca4c94f87a4e0b993de987cd
/frameworks/base/core/java/android/view/Window.java
|
b6c2624c8d9ee71d1c8d0aaf8082f92bb84b1418 |
|
22-Oct-2015 |
Robert Carr <racarr@google.com> |
Add window setDecorView API. Add a Window API for setting a view which will be placed in the decoration area (next to the window control buttons). Change-Id: Ie106cbea653ff95fdba987a2a43506d394600612
/frameworks/base/core/java/android/view/Window.java
|
9b3444256843296f1688aa1178bb2527dd01f250 |
|
16-Oct-2015 |
Wale Ogunwale <ogunwale@google.com> |
Use StringBuilder to construct window title string. Change-Id: I9193b7f5180f165d517cbfe0345f84e161b851d2
/frameworks/base/core/java/android/view/Window.java
|
d4f2b641d32f4c0f73b21c4436e5a14c4f569633 |
|
16-Oct-2015 |
Wale Ogunwale <ogunwale@google.com> |
am be02134c: am fceaedda: am 75693994: Merge "Disassociate system windows from apps" * commit 'be02134cbc7ef98e73f118aba45a92908d818553': Disassociate system windows from apps
|
ff58e30aca710252703e32bd7533abaa19a50487 |
|
13-Oct-2015 |
tiger_huang <tiger_huang@htc.com> |
Disassociate system windows from apps With the original logic, if an app creates a system window, when the user goes to home screen, the system window will be still there and become unable to receive input events, because the system window will be also changed to the stopped state with the app window, and the current logic of ViewRootImpl forbid a stopped window receiving input events. This change prevents assigning the token of the app window to system windows created by the app, so that when the app goes to the stopped state, its system windows won't be affected (can still receive input events). This change is related to the following changes: https://android.googlesource.com/platform/frameworks/base/+/a5d29971f8f4d463348e9de0f7af7e2e92a377a0 https://android.googlesource.com/platform/frameworks/base/+/15ed2754a308546a54ab1061b4e365d6fe9b898d https://android.googlesource.com/platform/frameworks/base/+/c3672cd3f7e2bd87d6de9dada499de82b62fae84 https://android.googlesource.com/platform/frameworks/base/+/41725dedc33906aaafee36b2d6523596e2a8a52e Bug: https://code.google.com/p/android/issues/detail?id=189710 Change-Id: I515e47bafcf39a2b1bdf92f11f623bef8fb6263c
/frameworks/base/core/java/android/view/Window.java
|
14418daa093f8cd39b7fccbc24115a6968dc8e92 |
|
05-Oct-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Fix recents crashing during docked stack resize. Whether acitvity window should be preserved during the relaunch is controlled by the activity manager and the existence of non-client-decor should not affect it. For example, docked activities will not have non-client-decor, but we would like to preserve them anyway. Bug: 24573657 Change-Id: I5d4852c3b7c26ac3ec1bbc105639f75b67d1d3ad
/frameworks/base/core/java/android/view/Window.java
|
0daf2102a20d224edeb4ee45dd4ee91889ef3e0c |
|
29-Sep-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Fix leaking the first activity while preserving windows. This is achieved by not having the decor view hold onto the activity context. Instead, we are wrapping application context, so that we can have theme support and also have a special instance of window manager that is aware of the phone window (the same way as activity do). This reverts commit a5ffea3b7d323cb57c0f9872468dd5c2e2ec66bb. Change-Id: I924f4c7ef8f0d20e9174bd7b3e00ec00b44443b9
/frameworks/base/core/java/android/view/Window.java
|
a59ac9cd645d25f03e4e488100bd99f92e83a3a7 |
|
11-Sep-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Preserve window during resize triggered relaunches. This changes application code behavior when the activity relaunches due to configuration change. It only applies to scenarios, where the configuration change was triggered by a user generated resize of an activity (i.e. user drags a corner of an activity and thus changes its size). Preserving a window means that we will keep the decor view and non client decor view around, but remove all children views when the activity gets destroyed. When the activity gets created again, it will attach its new content to the preserved view hierarchy. Mind, we actually recreate application side Window object, since some of its features might changed, but we retain its elevation (to not trigger relayout with new layout params). Preserving the window also means that we don't call the window manager service to remove and later add the window. Instead, we continue using a single window state throughout the resize operation. Change-Id: Ie3d2878ed09c99ff343044bfe7a29a0ba07a265e
/frameworks/base/core/java/android/view/Window.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/Window.java
|
4aef7c859459dcb52e9112444506a2db8f1a5d04 |
|
04-Sep-2015 |
Alan Viverette <alanv@google.com> |
Deprecate FEATURE_PROGRESS and related methods Bug: 23763003 Change-Id: I4ef97e089db592e438a27657faffa1c8290f2b0e
/frameworks/base/core/java/android/view/Window.java
|
f36bb0ca99ce2041b68faf650d8c807cfaa2bf95 |
|
26-Aug-2015 |
Skuhne <skuhne@google.com> |
Bring an activity to the front upon click & drag Clicking on the control area of a window should bring it to the top and set the focus since it might be used as a drag operation which would move / resize it. Bug: 23179116 Change-Id: I672bfefa42dd85e962fe343aeb89167ce125f168
/frameworks/base/core/java/android/view/Window.java
|
ce2faa5871e3bf5ec8407506df18bed209dd824c |
|
11-Aug-2015 |
Skuhne <skuhne@google.com> |
Adding API to access / change the task bounds Bug: 21738328 Change-Id: I3aabcbe1dcc5caa70f66554157f41fbfacf4c50f
/frameworks/base/core/java/android/view/Window.java
|
c6feec04530c31774ce6a84cca2d071ca282c910 |
|
08-Aug-2015 |
Stefan Kuhne <skuhne@google.com> |
Merge "Adding actions to non client decor buttons"
|
1b42057707dce8039326492e89a766f397043aa8 |
|
07-Aug-2015 |
Stefan Kuhne <skuhne@google.com> |
Adding actions to non client decor buttons This patch requires CL 744205 to be landed first. Bug: 22881983 Change-Id: I1bbce52e18719adcd09c7e70e09c37ec33387b04
/frameworks/base/core/java/android/view/Window.java
|
9bad7410e5b2235484cc550051bb8be9c671fd50 |
|
07-Aug-2015 |
Stefan Kuhne <skuhne@google.com> |
Adding missing WindowStackCallback to Window Bug: 22984908 Change-Id: I0efe210c2e1d2efba3e3ca20e6db393a904f28b9
/frameworks/base/core/java/android/view/Window.java
|
868a5e16c3f40a1c36bc2bd15891e930800e781a |
|
03-Aug-2015 |
Wale Ogunwale <ogunwale@google.com> |
Support for an activity to change and/or query it's associated stack Change-Id: I4fc1b47e5d6196a56a6e40f10fae97219554722c
/frameworks/base/core/java/android/view/Window.java
|
ba7881c89e7dd50aa537e70f0b96273e131dd08e |
|
02-Aug-2015 |
Wale Ogunwale <ogunwale@google.com> |
Support finishing a task with any finishing activity in the task. Change-Id: I8c6bb864de6dc135e0fedb16ee424d7816ee3cfa
/frameworks/base/core/java/android/view/Window.java
|
5aec62eae12b35de8d5fe7cba29166048c167572 |
|
08-May-2015 |
George Mount <mount@google.com> |
Remove hidden/deleted APIs. Change-Id: Iabeaac2c9b485f1f25fb2fcc3193610b0d6478c4
/frameworks/base/core/java/android/view/Window.java
|
0a4dc2258fa8216920e1a0b83cbf7d3729386e2f |
|
14-Apr-2015 |
Wale Ogunwale <ogunwale@google.com> |
Added TYPE_APPLICATION_ABOVE_SUB_PANEL window type. TYPE_APPLICATION_ABOVE_SUB_PANEL will be displayed on top of their attached window and any TYPE_APPLICATION_SUB_PANEL panels. Bug: 20135562 Change-Id: I711de3c19c01432c44de205bf09934a8b23b53fd
/frameworks/base/core/java/android/view/Window.java
|
6a975b3c3597a4ad9202432f3c3d867a03d43fa4 |
|
10-Apr-2015 |
Tim Kilbourn <tkilbourn@google.com> |
Save search context when dispatching onSearchRequested. The InputDevice used to trigger the search is saved in a SearchEvent so an application implementing onSearchRequested determine the device triggering the search. Bug: 15374820 Change-Id: If2cd14f77ce572a5ee131697cd63145fbea63f27
/frameworks/base/core/java/android/view/Window.java
|
bc4cf00dc5bf6e0e3c01206d5c46e64306df260a |
|
25-Mar-2015 |
John Spurlock <jspurlock@google.com> |
Fix a few found doc problems. Change-Id: I98567f4a0fc96f501c00bf361688e2c55232f78d
/frameworks/base/core/java/android/view/Window.java
|
da81fa569ed2f955252d69c1e000ebc1a2850191 |
|
16-Mar-2015 |
Tor Norbye <tnorbye@google.com> |
Merge "Add resource type annotations to some APIs"
|
417ee5ba89f7e0fe5efd34fce74bf1ee5923d976 |
|
11-Mar-2015 |
Tor Norbye <tnorbye@google.com> |
Add resource type annotations to some APIs Change-Id: I37c8afdaea455aa92bc8270bb2dfd60616c5f9bc
/frameworks/base/core/java/android/view/Window.java
|
4423d91de5300d3fd318bf5bc2d4d7e5bb856abf |
|
02-Mar-2015 |
Clara Bayarri <clarabayarri@google.com> |
Add a type parameter to startActionMode() calls. This requires adding a new method to View and Window.Callback to pass down the type as a parameter. For compatibility purposes, the new method implementations keep the type and call the old method, in case clients have subclassed it. Change-Id: If5d857f131e33be8cc6a8814f2e9c4e85ad2da25
/frameworks/base/core/java/android/view/Window.java
|
80756e38882720860db52f1fcc21fa1505a02abf |
|
02-Mar-2015 |
Tor Norbye <tnorbye@google.com> |
Annotate ARGB integer parameters with @ColorInt Change-Id: I307f72a382272cf18ddb6b07d9fcb81228568d9a
/frameworks/base/core/java/android/view/Window.java
|
7b9c912f536925ac6ec43935d6e97506851b33d6 |
|
31-May-2013 |
Tor Norbye <tnorbye@google.com> |
Add @ResourceInt annotations on APIs Change-Id: I119cc059c2f8bd98fd585fc84ac2b1b7d5892a08
/frameworks/base/core/java/android/view/Window.java
|
c051955392840cb94bd6f0b2a8107a48d2ffc8b0 |
|
12-Feb-2015 |
Scott Kennedy <skennedy@google.com> |
Mark findViewById(int) @Nullable Change-Id: I9bf7c08a896bd9c28400ff832179abc579fd502f
/frameworks/base/core/java/android/view/Window.java
|
b10e33ff804a831c71be9303146cea892b9aeb5d |
|
04-Feb-2015 |
Jorim Jaggi <jjaggi@google.com> |
Split up android.policy into framework.jar and services.jar 1/3 Change-Id: Ifd69f1f3dd308a7e17a1442e2f3950da8b03cec4
/frameworks/base/core/java/android/view/Window.java
|
c3a043cf0e1c91dcffc2cd596908266ba92a4c28 |
|
04-Feb-2015 |
George Mount <mount@google.com> |
Fix TODO in javadoc for FEATURE_CONTENT_TRANSITIONS. Bug 19254085 Change-Id: I22d4c4e3d1d754ab96741eb0e0290d1ecfc05552
/frameworks/base/core/java/android/view/Window.java
|
aa1008cba4b97a269f65f86534d994347b6cdeff |
|
13-Jan-2015 |
Bryce Lee <brycelee@google.com> |
Update javadoc for DEFAULT_FEATURES deprecation. Bug: 18983343 Change-Id: I10936e292edf9146e7acca231632fb704054215c
/frameworks/base/core/java/android/view/Window.java
|
71922de6c8e407ff24bb1a500cb53bb1a647c758 |
|
13-Jan-2015 |
Alan Viverette <alanv@google.com> |
Update docs for Window.setElevation(), apply changes immediately BUG: 18983689 Change-Id: I471104092d6296dc0ba2689da96783be088fbce8
/frameworks/base/core/java/android/view/Window.java
|
fe568359340e58492e2ca1ebdab0f234b91e328a |
|
05-Jan-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Add system api for disabling touch events in wallpaper behind the window. Bug: 18721756 Change-Id: I40b749a9916536d52042e5dd49a23575bedad754
/frameworks/base/core/java/android/view/Window.java
|
3a0d878ab56475276c61d574af7651820a5cea5a |
|
04-Dec-2014 |
Svetoslav <svetoslavganov@google.com> |
Ensure all events from a showing window are dispatched. Accessibility services may opt-in to introspect the interactive windows on the screen. If window introspection is enabled there is a case where some events from a showing window are received before the updated window state from the window manager. Now the window manager sends over the windows before notifying the app for the focus change. bug:18625996 Change-Id: Ic481e01efbe12dc92f090f799feeb236672fc7b3
/frameworks/base/core/java/android/view/Window.java
|
d6e6e7235a7e5c82d64beada54ac89c2b1dec201 |
|
21-Nov-2014 |
Bryce Lee <brycelee@google.com> |
Make default windows features configurable. Bug: 18434078 Change-Id: I0bafce1a201088a8681f4b9e43237e23b49296a2
/frameworks/base/core/java/android/view/Window.java
|
79c067c54a944660438c81ac2caf37ec68eedfa9 |
|
29-Oct-2014 |
Alan Viverette <alanv@google.com> |
Add setters for window elevation and clipToOutline properties These are available as XML attributes but were lacking setters. None of the Window properties have getters, so just adding setters here. BUG: 16847753 Change-Id: I9c032903e94b7f12125210bd73c911243612df69
/frameworks/base/core/java/android/view/Window.java
|
9678e34521d7eaa38cd93bee32b1e307956b74bd |
|
25-Oct-2014 |
Alan Viverette <alanv@google.com> |
Clean up some javadocs in Window.setFeature...() Change-Id: I80812f9ce7a746ad9686aa4462f7570dfd9b4c0e
/frameworks/base/core/java/android/view/Window.java
|
393b1c1e88cbdd0f65c8f217c495dbbe8de9125d |
|
19-Oct-2014 |
Wale Ogunwale <ogunwale@google.com> |
Fix issue #17789629: PopupWindow overlaps with navigation bar. The Lollipop release introduced a feature that allowed apps to extend under the navigation bar. This also means any popup window that is anchored to the bottom of its parent window will overlap with the navigation bar if the parent window is extending underneath the navigation bar. This change introduces a new window flag (FLAG_LAYOUT_ATTACHED_IN_DECOR) that allows the app to specify if the popup window should be attached to the decor frame of the parent window thereby avoiding an overlap with the screen decorations. By default the flag is set on SDK version LOLLIPOP_MR1 or greater and cleared on lesser SDK versions. Also, replaced flags FLAG_NEEDS_MENU_KEY and PRIVATE_FLAG_NEEDS_MENU_KEY_SET with needsMenuKey state variable to make room for the new FLAG_LAYOUT_ATTACHED_IN_DECOR flag. Bug: 17789629 Change-Id: I2150e0c6ac688c966c0e8f7e54d42fd20285bea6
/frameworks/base/core/java/android/view/Window.java
|
9826f636ad4fe3714d60972acd918e09eb44d971 |
|
11-Sep-2014 |
George Mount <mount@google.com> |
Have Activity Transitions activited by a new window attribute. Bug 17006497 Window content transitions were being enabled by default in the Material Theme so that Activity Transitions could be enabled by default. Unfortunately, this gave the effect that many applications did not want -- the default transition between window content is a fade out/in. Here, a new attribute is added: windowActivityTransitions that is enabled by default in the Material theme and windowContentTransitions is disabled by default in all themes. Change-Id: Iab453d608f00a48ff7ab7f09ce84b52cf5f20294
/frameworks/base/core/java/android/view/Window.java
|
c03da0e7a9ef721709d51cf8a2d539a5bd8a320e |
|
23-Aug-2014 |
George Mount <mount@google.com> |
Make Fragment Transitions match Acitivty Transitions API Bug 17188255 Change-Id: I506a097be4010d7156caf465c95295c58612c16e
/frameworks/base/core/java/android/view/Window.java
|
fd63dd0ce20dbb4170d675938671f07a276ccd8f |
|
29-Aug-2014 |
RoboErik <epastern@google.com> |
Add javadoc to Window.set/getMediaController Fleshes out the javadoc a bit more instead of just a reference to the description of the methods in Activity. bug:17198774 Change-Id: I24afe1c5d9f2e46e201c84072a6b34a619867889
/frameworks/base/core/java/android/view/Window.java
|
b89d5cc2c64112a0ff7e66e4dd3bb2114caed935 |
|
19-Aug-2014 |
George Mount <mount@google.com> |
Allow Activities to opt into using Overlay for shared elements. Bug 17001227 Change-Id: Icc49a81357ee69abd2a15a1d1efcead298ab3fb7
/frameworks/base/core/java/android/view/Window.java
|
68f96d8db5e5e701b6a12b5cddecc985e56a26c6 |
|
31-Jul-2014 |
George Mount <mount@google.com> |
Add differentiating transitions for returning/reentering. Bug 16550363 Change-Id: I85f9a8bcbc92ce048d06b36579bb05893534f7f8
/frameworks/base/core/java/android/view/Window.java
|
550116576cce028d3c435f7c3ae9f6e3b92b5cf2 |
|
10-Jul-2014 |
RoboErik <epastern@google.com> |
Add API to set a default session in Activity We may have multiple remote sessions at once so an app needs a way to specify a default session to route media and volume commands to when its activity is in the foreground. This adds an api that works in parallel with the default stream api on Activity. bug:15727927 Change-Id: I5b67cb3e20647f9437d90aa65be63efe8c7865cf
/frameworks/base/core/java/android/view/Window.java
|
238010f056433d64e6eb27c45ab8124563651eba |
|
01-Jul-2014 |
George Mount <mount@google.com> |
Allow activity transitions to target nav and status bar colors. Bug 15885062 Action bar can already be targeted via android:action_bar. Navigation bar background is now android:navigation:background. Status bar background is now android:status:background. Change-Id: I4604906923f3473af3beec4f865463b2fe4a5316
/frameworks/base/core/java/android/view/Window.java
|
990205eada00ad3e575761d19607bb03e12f9aa3 |
|
24-Jun-2014 |
George Mount <mount@google.com> |
Don't use overlay to transition ImageViews. Bug 15744992 MoveImage used an overlay to transition ImageViews. This caused strange problems when ImageViews were contained in other Views. The new ChangeImageTransform does a smooth transition for changes in scale type and bounds. Change-Id: Ia5021f4828f8f818a8699b3bdd38437aeba1cfc8
/frameworks/base/core/java/android/view/Window.java
|
ed1e01d7e431edbcaab983b4b240418f2b090fac |
|
05-Jun-2014 |
George Mount <mount@google.com> |
Allow customization of background fade duration. Bug 15195468 Change-Id: I02c1ef446cfa8aaedce640ab5694b6d9245bb9f7
/frameworks/base/core/java/android/view/Window.java
|
ea56251d92050e9a672d1f66d0d4621e4dd4136e |
|
05-May-2014 |
Adrian Roos <roosa@google.com> |
Colorize SystemUI Makes the color of the status and navigation bars customizable by the app. Bug: 14564488 Change-Id: I036edc228cfe1b659c7f11a43cdc4598ee705ff8
/frameworks/base/core/java/android/view/Window.java
|
217ccd2f82031f05d111bce7308a65136f278c7a |
|
09-May-2014 |
Adrian Roos <roosa@google.com> |
Add System UI Color API Bug: 14564488 Change-Id: Ibebe87faeb1b730f9ac33bb5074a7b4f71b9d1c7
/frameworks/base/core/java/android/view/Window.java
|
5f97930fc5dd44fcf1864acd53401c00b4de3a24 |
|
06-May-2014 |
Adam Powell <adamp@google.com> |
am c41fa708: am a0516e7a: Merge "onWindowDismissed API cleanup" into klp-modular-dev * commit 'c41fa708271e204a7983aba291389ea1554227b2': onWindowDismissed API cleanup
|
117b695222135cc684e891d4126116b97a64bc9e |
|
06-May-2014 |
Adam Powell <adamp@google.com> |
onWindowDismissed API cleanup Move the window swipe to dismiss plumbing off of Window.Callback into its own internal interface implemented by Activity and Dialog. Make it internal API instead of public. Apps should control this via the window feature setting. Change-Id: I64cd237fa7eab08719b2c34e31dac7d34f02563a
/frameworks/base/core/java/android/view/Window.java
|
31a217290cf376d0573fc36e21c8940987485019 |
|
25-Mar-2014 |
George Mount <mount@google.com> |
Split Activity Transitions out of PhoneWindow. Bug 13622834 Made it possible to use shared elements without making Views invisible. Change-Id: I1e85c6bc19e634a9af225ad7f0309b4f003ea462
/frameworks/base/core/java/android/view/Window.java
|
cb4b7d999e7bcba608726188421772e313e67163 |
|
25-Feb-2014 |
George Mount <mount@google.com> |
Implement "Back" for Activity Transitions. Change-Id: Iceaf888f57f2c7598f9291687ac9ad76d55bd82c
/frameworks/base/core/java/android/view/Window.java
|
568628dc2cb92b3ec3a87cae9de3203fbdc5968c |
|
05-Mar-2014 |
Will Haldean Brown <haldean@google.com> |
Manually merge commit '2faf28cf' into master Original commit message: Add swipe-to-dismiss support to PhoneWindow. This adds a new window feature -- FEATURE_SWIPE_TO_DISMISS -- and a theme attribute to activate that feature. When the feature is activated, a SwipeDismissLayout is inflated as the DecorView layout. SwipeDismissLayout intercepts touch events and steals ones that are large swipes to the right if its children don't. PhoneWindow registers handlers that listen for these swipe events, translate the window when necessary, and finish the activity at the end of the gesture. Conflicts: core/java/android/view/Window.java core/res/res/values/attrs.xml Change-Id: I943290b436864ca4a1bd401b88d696e08c921cdd
|
ca6234e084a71e0c968cff404620298bcd971fcc |
|
12-Feb-2014 |
Will Haldean Brown <haldean@google.com> |
Add swipe-to-dismiss support to PhoneWindow. This adds a new window feature -- FEATURE_SWIPE_TO_DISMISS -- and a theme attribute to activate that feature. When the feature is activated, a SwipeDismissLayout is inflated as the DecorView layout. SwipeDismissLayout intercepts touch events and steals ones that are large swipes to the right if its children don't. PhoneWindow registers handlers that listen for these swipe events, translate the window when necessary, and finish the activity at the end of the gesture. Change-Id: I512e758f3c3ffd3b353dba3b911c0e80a88d6f5f
/frameworks/base/core/java/android/view/Window.java
|
e180337ee99b9155fe441ea55451f4d2167b5d9a |
|
26-Feb-2014 |
George Mount <mount@google.com> |
Change Activity Scene Transitions to be more automatic redo. This reverts commit 206e30cd93afe3eb72ec94178324417db5424ed2 along with removing the additional startActivity* methods and replaces them with ActivityOptions makeSceneTransitionAnimation methods. Change-Id: I52bec31ae3c4cea6d549810ae5a7acd8aea176d8
/frameworks/base/core/java/android/view/Window.java
|
206e30cd93afe3eb72ec94178324417db5424ed2 |
|
26-Feb-2014 |
George Mount <mount@google.com> |
Revert "Change Activity Scene Transitions to be more automatic." This reverts commit f10587faadb9080a7bf9991cbe04bac5525da482. Change-Id: I2785a3d2d6b667cad6d61dcbbc1c624161735fa4
/frameworks/base/core/java/android/view/Window.java
|
f10587faadb9080a7bf9991cbe04bac5525da482 |
|
06-Feb-2014 |
George Mount <mount@google.com> |
Change Activity Scene Transitions to be more automatic. Shared element transitions are enabled by default when the Window has a TransitionManager. Shared element location and size are captured and transferred to the target Activity. ActionBar is treated as a shared element. Change-Id: I0f22ea4e5cbe80254e848444e3f235cb742684f4
/frameworks/base/core/java/android/view/Window.java
|
0a778eda690a66173733a63622886e888d405c45 |
|
13-Dec-2013 |
George Mount <mount@google.com> |
Cross-Activity Scene transition API. First pass at API for cross-Activity Scene transitions. Remaining work: Transition back Automatically capture hero element info Transfer of surface texture to synchronize between Activities Possibly use scene names to indicate preferred transition Change-Id: I59d07de1fae694a46b92b1c82525daa301ec1377
/frameworks/base/core/java/android/view/Window.java
|
8eea3ea5591e59f55cbb4f6b2b7e9363a285ced3 |
|
04-Feb-2014 |
Alan Viverette <alanv@google.com> |
Add APIs for obtaining themed Drawable from Theme, Context BUG: 12611005 Change-Id: Ic0057be4e4c2d0c61ce02a019b3f7d0625e3a016
/frameworks/base/core/java/android/view/Window.java
|
cfbe9be5b3b701d95fb24fa0f7c8d9be43eec776 |
|
06-Nov-2013 |
Adam Powell <adamp@google.com> |
Add support for cross-activity scenes and transitions * Add theme attributes for specifying a top-level TransitionManager for an activity window. * Add window feature for automatic content transitions. This automatically assigns/creates a Scene for setContentView calls. * Add named transitions. This allows apps to define APIs for handshake-agreements about which exit/entrance transitions to play. * Add new transition type for ActivityOptions. This lets the system use ActivityOptions to communicate transition specifics and arguments to the called activity. * Have ActivityManager pass appropriate ActivityOptions through to the called Activity. Have the called activity call back into the caller to let it know which transition of a possible requested set was chosen. Still to do: * Define and pass arguments for transitions. This will require defining a Parcelable version of TransitionValues and deciding how much leeway apps should have for these things. * Determine how to appropriately filter the ActivityOptions bundle so that only appropriate data reaches the target. * Determine if generalizing the auto-Scenes functionality to ViewGroups is appropriate. Change-Id: I10684b926129ab2fbc1adec9ef31767237acae79
/frameworks/base/core/java/android/view/Window.java
|
2525d9c8437c34440e4df0583f333a06a5c4fc10 |
|
15-Nov-2013 |
Alan Viverette <alanv@google.com> |
Deprecate Activity.setTitleColor() BUG: 11712103 Change-Id: Id34ffb59d3f848c591a98880c6cdd9058e5a38dc
/frameworks/base/core/java/android/view/Window.java
|
18e905f42d017c4721d33bd25d7d39ef8d64b5d5 |
|
24-Oct-2013 |
Adam Powell <adamp@google.com> |
Make Scenes and Transitions first-class in PhoneWindow/Themes Add a window feature for content transitions. This implicitly creates a Scene for each setContentView operation and runs the appropriate transition. Applications can specify a TransitionManager XML in their theme that will apply the appropriate transitions when these implicit scene changes occur. Apps can specify a "to" with no "from" in a transition to request an entrance transition for the given content. This lays the groundwork for further full content change/activity to activity transitions. Change-Id: Ic815d9e0b9ce958152d70bf6ee01be075aa9fe88
/frameworks/base/core/java/android/view/Window.java
|
38dc2ad85e4572d6e56f0a98edd97945312f708c |
|
04-Oct-2013 |
Adam Lesinski <adamlesinski@google.com> |
am b2db2fbc: am 6d90862f: am d65825ab: Merge "Private flags are masked in correct variable" into klp-dev * commit 'b2db2fbce33dbcfa52ccb20267ad4897c558c34f': Private flags are masked in correct variable
|
95c42974f719d1fac90fc0438eac778e9795681f |
|
02-Oct-2013 |
Adam Lesinski <adamlesinski@google.com> |
Private flags are masked in correct variable Newly added private flags were being masked in the public flag variable as opposed to the correct privateFlags variable. bug:11033280 bug:11043194 Change-Id: Idda3a70a083457f3f1b7d4b46d231f4a7e704cf0
/frameworks/base/core/java/android/view/Window.java
|
d9273d6f289d9b55da3fd0db2f659fdfb48106a8 |
|
31-May-2013 |
Tor Norbye <tnorbye@google.com> |
Add typedefs and nullness annotations. This changeset adds in typedef annotations (custom annotations marked with @IntDef) for various int parameters and return values in the API. It also adds nullness annotations for cases where the documentation explicitly mentioned null policy, or where it was blindingly obvious from the context. Also fixed some typos in the documentation. Change-Id: Ica27c01368895818e26237544edd8483007155bb
/frameworks/base/core/java/android/view/Window.java
|
30f420fd6a74ffa28b351b4aba74d44f5ea48dda |
|
02-Aug-2013 |
keunyoung <keunyoung@google.com> |
add local focus mode and input event injection API to Window - This enables keyboard navigation for window without focus. - FLAG_LOCAL_FOCUS_MODE puts window into local focus mode. - Application needs to put window in local focus mode, control focus, and inject events to make dpad navigation work. - Window in local focus mode does not interact with window manager or ime regarding focus related events. - Also renamed ViewRootImpl.dispatchKey to dispatchInputEvent to allow both key and touch events injection. Change-Id: I8e8561f29e0dade3797fb7ae3ee7690e6b7f8895
/frameworks/base/core/java/android/view/Window.java
|
04fe6ebb9f919f196ec06a19bebc09b8e943f95b |
|
31-May-2013 |
Adam Powell <adamp@google.com> |
Fix a bug resolving the correct icon/logo in action bars Remove some abstraction-breaking magic in ActionBarView and replace it with proper resolution of the icon/logo when creating a window. The old implementation relied on the ActionBarView's context being an Activity. Bug 9171554 Change-Id: Idbbb1942622195dcb55e8119f2d64287b07bb509
/frameworks/base/core/java/android/view/Window.java
|
4b6d93fd0485b46a3a15a71516d39b4f72d9b3db |
|
19-Sep-2012 |
Adam Powell <adamp@google.com> |
Make invalidateOptionsMenu asynchronous Process any pending menu invalidations on the animation tick, before traversals are performed. Collapse multiple menu invalidations together. Bug 7189372 Change-Id: I7a33ae9813980eb8fbcc958804de2c03328ecca8
/frameworks/base/core/java/android/view/Window.java
|
98365d7663cbd82979a5700faf0050220b01084d |
|
20-Aug-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor for multi-display support. Split WindowManagerImpl into two parts, the WindowManager interface implementation remains where it is but the global communications with the window manager are now handled by the WindowManagerGlobal class. This change greatly simplifies the challenge of having separate WindowManager instances for each Context. Removed WindowManagerImpl.getDefault(). This represents the bulk of this change. Most of the usages of this method were either to perform global functions (now handled by WindowManagerGlobal) or to obtain the default display (now handled by DisplayManager). Explicitly associate each new window with a display and make the Display object available to the View hierarchy. Add stubs for some new display manager API features. Start to split apart the concepts of display id and layer stack. since they operate at different layers of abstraction. While it's true that each logical display uniquely corresponds to a surface flinger layer stack, it is not necessarily the case that they must use the same ids. Added Display.getLayerStack() and started using it in places where it was relatively easy to do. Change-Id: I29ed909114dec86807c4d3a5059c3fa0358bea61
/frameworks/base/core/java/android/view/Window.java
|
d32460c5b7bea7b06e345397fdbaca58d9732dcf |
|
21-Jul-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor local window manager implementation. The objective of this refactoring is to remove the reliance on WindowManager wrapper objects for compatibility mode and for managing sub-windows. Removed the WindowManager.isHardwareAccelerated() method since it is never used. Change-Id: I4840a6353121859a5e0c07d5cc307a437c595d63
/frameworks/base/core/java/android/view/Window.java
|
193fc075a2a19517c175a5760fc5e9f10d0f2e31 |
|
04-Jun-2012 |
Christopher Tate <ctate@google.com> |
Docs tweak Cross-reference the flag manipulation methods in Window to make it easier to discover them. Change-Id: I81ef38fd69b43683e4ec8d48c058496470533b53
/frameworks/base/core/java/android/view/Window.java
|
3a3a6cfd8ec12208ca75c0d0d871d19d76c34194 |
|
26-Mar-2012 |
Dianne Hackborn <hackbod@google.com> |
Add new feature to let apps layout over status bar / system bar. The main change is a few new flags you can supply to View.setSystemUiVisibility(). One is a new visibility mode, SYSTEM_UI_FLAG_FULLSCREEN, which is basically the same as the global FLAG_FULLSCREEN option for windows, but driven as part of the system UI state. There are also three new flags for telling the framework that you would like to have your application's UI ignore screen decorations -- SYSTEM_UI_FLAG_LAYOUT_NO_NAVIGATION for going behind the navigation bar and SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN for ignoring full screen decorations (that is the status bar). In combination with this you can use SYSTEM_UI_FLAG_LAYOUT_STABLE to have the framework report consistent insets to your application. When using NO_NAVIGATION, when the user taps the screen we now also automatically clear ONLY_CONTENT, so that we atomically show both UI elements. This should make it easy for apps like video players that want to move between fully full-screen and regular modes. The ActionBar has also been extended when in overlay mode so that it will adjust the system window insets to also account for its space, and allow it to be hidden using the new SYSTEM_UI_FLAG_FULLSCREEN. Change-Id: Ic8db1adec49a0f420bfe40c1d92eb21307856d0b
/frameworks/base/core/java/android/view/Window.java
|
73ab6a49db2b834ce1d56c7a1164938b409ee6fc |
|
13-Dec-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5755172: Soft menu key disappears when menu is open We need to work more like before in determining whether the menu key is needed -- in some cases look back in the window list to determine this if we don't know the value from the current window. This requires adding a new private flag indicating whether the compat menu state is known for a window, which is set by PhoneWindow as part of its existing process of computing the flag for its own windows. Now we can have a new API on WindowState to determine the value of this flag for a window, which if needed walks back in the window list to find a window the value is known for (or stops at what the policy has determined is the top full-screen window, so we stop like we used to at things like the lock screen or the bottom of an application). Change-Id: I829de6d629b5af8bcb422cb85249ee4041c7205e
/frameworks/base/core/java/android/view/Window.java
|
9622e20486955e3a3c2f45c61b23650fb35e6559 |
|
30-Sep-2011 |
Romain Guy <romainguy@google.com> |
Add system property to force hw acceleration. Change-Id: I538e641435f282b1af20866a8acd1f8d292734c4
/frameworks/base/core/java/android/view/Window.java
|
661cd52e0e1d527132eb1cae604d3e64da7ec0cb |
|
22-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Add progress dialog for booting after an upgrade. This introduces a new facility for code during the boot process to display messages to the user through a progress dialog. This is only for use when performing longer-than-usual post-upgrade operations such as running dexopt on applications or upgrading databases. Change-Id: I0e78439ccec3850fb67872c22f235bf12a158dae
/frameworks/base/core/java/android/view/Window.java
|
e43fca99573291311f90b540d67833011d5fc6be |
|
16-Aug-2011 |
Adam Powell <adamp@google.com> |
Offer a masked version of setUiOptions for windows to only modify certain flags. Change-Id: I36aaff982767f8984c468e8c13f8d5ec8c3c0040
/frameworks/base/core/java/android/view/Window.java
|
269248d112e35fe8e9f0d5d11c96dcb2ac1118b0 |
|
02-Aug-2011 |
Adam Powell <adamp@google.com> |
Fix bug 5098288 - Rethink the suite of new themes Cut down the list of new themes for ICS. Holo apps now have Theme.Holo, Theme.Holo.Light, and Theme.Holo.Light.DarkActionBar to choose from. Add manifest attribute android:uiOptions to express splitActionBarWhenNarrow. Other options may move into this later as well. (DialogWhenLarge?) This attribute is valid on both activity and application tags; application settings will serve as the default for activities that do not explicitly set uiOptions. uiOptions are not currently reflected in the startup window for new activities. Change-Id: Iffdc2ce4cc69f79c9bd4e541b7923286e6936c1e
/frameworks/base/core/java/android/view/Window.java
|
5fd2169eabd77e6bfafaf456e58051a3bafb2bca |
|
07-Jun-2011 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #4518815: Compatibility mode introduces compatibility regression... ...for Market App iRunner There were a lot of serious issues with how we updated (or often didn't update) the display and resource state when switching compatibility mode in conjunction with restarting and updating application components. This addresses everything I could find. Unfortunately it does *not* fix this particular app. I am starting to think this is just an issue in the app. This change does fix a number of other problems I could repro, such as switching the compatibility mode of an IME. Also a few changes here and there to get rid of $#*&^!! debug logs. Change-Id: Ib15572eac9ec93b4b9966ddcbbc830ce9dec1317
/frameworks/base/core/java/android/view/Window.java
|
5be8de3420ba4c9d816b98e29bdec11715f6b626 |
|
25-May-2011 |
Dianne Hackborn <hackbod@google.com> |
More compatibility mode improvements. We now correctly adjust display metrics, fixing for example issues seen in Barcode Scanner. In addition the decision about when to use compatibility mode has a bug fixed where certain apps would not go out of compatibility mode even though they should be able to. Change-Id: I5971206323df0f11ce653d1c790c700f457f0582
/frameworks/base/core/java/android/view/Window.java
|
310ae9b39c10f6b43c885e458eb8d135a3ba6b71 |
|
19-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
am fe86e979: am 661b6cfb: Merge "Okay, new plan for dialogs." into honeycomb * commit 'fe86e9793ce62c6a1aa34e5712f16b45800efdd0': Okay, new plan for dialogs.
|
7fc5d4b8e7145413411da3320495388f09fab536 |
|
19-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
am 2ec5a716: am 36c84403: Merge "Fix issue #3362484: Can\'t dismiss activity picker by tapping outside dialog" into honeycomb * commit '2ec5a7160b3d32887b2428edef7a751ee3700809': Fix issue #3362484: Can't dismiss activity picker by tapping outside dialog
|
ef57575887bde74ef09e9f21aae6b02f9c8163c7 |
|
19-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
Okay, new plan for dialogs. Don't dismiss by default when tapping outside, even for AlertDialog. If AlertDialog doesn't have any buttons, tapping outside will dismiss it. Applications can make their own dialogs (or activities looking like dialogs) can use the existing and new APIs to control this behavior themselves so that it does the right thing. Change-Id: I02bfb9161e169de0033200211b3a7ec80080bd83
/frameworks/base/core/java/android/view/Window.java
|
cfaf8878de83b6bb7a24aee3c240259f428e6e4a |
|
18-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #3362484: Can't dismiss activity picker by tapping outside dialog Change-Id: Idc2fe5a86c61e8f94fe9d902a0087a05f6f7918e
/frameworks/base/core/java/android/view/Window.java
|
cb1404e45639d20439d7700b06d57ca1a1aad1fa |
|
16-Jan-2011 |
Jeff Brown <jeffbrown@google.com> |
Add joystick support to framework. Change-Id: I95374436708752e1a9cff3f85c5b9bc3e0987961
/frameworks/base/core/java/android/view/Window.java
|
64da12ab1f472e01325b6c6d094153ac110eaf7b |
|
05-Jan-2011 |
Jeff Brown <jeffbrown@google.com> |
Add dispatch key shortcut window callback. Enables Activities and Dialogs to implement key shortcut behavior. Useful for global key shortcuts that are not bound to the focused view or to a menu. Change-Id: If377d20b227ee1c5cac84c47c9630b2d77f67e2c
/frameworks/base/core/java/android/view/Window.java
|
c91893511dc1b9e634648406c9ae61b15476e65d |
|
15-Dec-2010 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #3272082: Contacts: when going back from edit view, list UI is not ready yet This involves some reworking of Loaders. Loaders, in particular CursorLoader, are now expected to retain their current data after being stopped. This allows applications to keep that data across onStop() -> onStart(), so when the user returns to the app it doesn't have to wait for the data to reload and thus cause flicker. This includes various API changes to better reflect the new semantics, plus a new LoaderCallbacks method to tell the application when it is actually time to stop their use of a loader's data. Note this is somewhat half-done, to help checking in the extensive application changes that are required without causing build breakage. Change-Id: Ib4b3bf8185a6da46e7f06ca125521d65e2e380a1
/frameworks/base/core/java/android/view/Window.java
|
debf3bed9ea913ac55c80e1f9f7f33217054a943 |
|
16-Nov-2010 |
Adam Powell <adamp@google.com> |
Fix bug 2948913 - provide lifecycle notifications for action modes Change-Id: I432e29a7bddb18bc32dfbe21a8ecd7d83158e3a0
/frameworks/base/core/java/android/view/Window.java
|
7eec10e6c99c30d5ee061fec08ac89ad4254ac32 |
|
13-Nov-2010 |
Dianne Hackborn <hackbod@google.com> |
Get rid of the extended themes. We now decide whether to use a bitmap background based on whether the window's drawing is hardware accelerated. To do this, there is a new "state_accelerated" that state list drawables can be parameterized on, and the standard window background uses this to select a solid color or bitmap drawable as appropriate. Introduces a little hackery to have wm preview windows pretend like they are hardware accelerated even if they aren't, so the preview looks closer to the actual app. Also Add a DialogWhenLarge variation for the light theme. Change-Id: I215a79d5df65ba3eed52ab363cade9d8218a6588
/frameworks/base/core/java/android/view/Window.java
|
806de5b1c5f98d67b00f7ba6087faca3b9632845 |
|
23-Sep-2010 |
Romain Guy <romainguy@android.com> |
Remove unused constant. Change-Id: I02e8f76cc1406e693f822822808b3485d2158884
/frameworks/base/core/java/android/view/Window.java
|
f4a6ec4e9398c1beb019e1c208272bf56401f925 |
|
24-Aug-2010 |
Adam Powell <adamp@google.com> |
Disable FEATURE_ACTION_BAR on windows with incompatible feature sets. Change-Id: I70c860c72eb9e1f1f123764202334ab714f4f830
/frameworks/base/core/java/android/view/Window.java
|
291905e34a7f0ae03c68fb2c1b8c34b92d447fbf |
|
18-Aug-2010 |
Dianne Hackborn <hackbod@google.com> |
Maybe fix #2925641: calling onCreateOptionsMenu before attached activity Also add some APIs to PreferenceActivity. Change-Id: I85894a3eb9cd3e5adb78b82e85454c0d74773178
/frameworks/base/core/java/android/view/Window.java
|
6b336f835d637853800b94689375a03f337139a4 |
|
11-Aug-2010 |
Adam Powell <adamp@google.com> |
ActionBar overlay mode, height fetching, show/hide Change-Id: Ie931ed26ec885d891d6733132b517a53d95f8491
/frameworks/base/core/java/android/view/Window.java
|
529b60a3b16ac3dff24f2403d760ab8ebc9670ff |
|
04-Aug-2010 |
Romain Guy <romainguy@google.com> |
Add android:hardwareAccelerated to Activity. Hardware acceleration can now be enabled/disabled locally on each activity declared in the manifest. It can also be enabled/disabled directly on a window through the WindowManager.LayoutParams. Change-Id: I91dd0b26c4e7eb8cd7288e523ed6b7bda6d0990b
/frameworks/base/core/java/android/view/Window.java
|
5d27977f9da482627ceb19317a2cd70467aff046 |
|
28-Jul-2010 |
Adam Powell <adamp@google.com> |
Action modes without action bar Change-Id: I0367ab35e598a17980bd373b30828175f6283acc
/frameworks/base/core/java/android/view/Window.java
|
ac670c0433d19397d4e36ced2110475b6f54fe26 |
|
28-Jul-2010 |
Romain Guy <romainguy@google.com> |
Generate shaders to cover all possible cases. With this change, all the vertex and fragment shaders used by the GL renderer are now generated based on a program description supplied by the caller. This allows the renderer to generate a large number of shaders without having to write all the possible combinations by hand. The generated shaders are stored in a program cache. Change-Id: If54d286e77ae021c724d42090da476df12a18ebb
/frameworks/base/core/java/android/view/Window.java
|
6e34636749217654f43221885afb7a29bb5ca96a |
|
23-Jul-2010 |
Adam Powell <adamp@google.com> |
Moved context modes into view, renamed to action modes ContextualMode renamed to ActionMode. Adds a reference to the action bar and reduces confusion around things named "Context". Change-Id: Ia5098b1d0799a0ece0810c34e6696eda039fb005
/frameworks/base/core/java/android/view/Window.java
|
2388ad9eef109fa7f63c196c819c83f0376f0645 |
|
14-Jul-2010 |
Dianne Hackborn <hackbod@google.com> |
am f8d9379b: am d76b67c3: IME events are now dispatched to native applications. Merge commit 'f8d9379bd834573feca085284970cf686993c330' * commit 'f8d9379bd834573feca085284970cf686993c330': IME events are now dispatched to native applications.
|
d76b67c340d1564abf8d14d976fdaf83bf2b3320 |
|
14-Jul-2010 |
Dianne Hackborn <hackbod@google.com> |
IME events are now dispatched to native applications. And also: - APIs to show and hide the IME, and control its interaction with the app. - APIs to tell the app when its window resizes and needs to be redrawn. - API to tell the app the content rectangle of its window (to layout around the IME or status bar). There is still a problem with IME interaction -- we need a way for the app to deliver events to the IME before it handles them, so that for example the back key will close the IME instead of finishing the app. Change-Id: I37b75fc2ec533750ef36ca3aedd2f0cc0b5813cd
/frameworks/base/core/java/android/view/Window.java
|
f92f8686f982c62a609a2087383a77a24d126992 |
|
23-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
am 98f7aed6: am 1e4b9f39: Remove InputConsumer, replacing with InputQueue. Merge commit '98f7aed66b54c365f816fe990de978f61155cde1' * commit '98f7aed66b54c365f816fe990de978f61155cde1': Remove InputConsumer, replacing with InputQueue.
|
1e4b9f3936d6f357e89360293e05a0e16d5fa440 |
|
23-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
Remove InputConsumer, replacing with InputQueue. Change-Id: Ib06907278457aaee842b123adc072840ca3602d8
/frameworks/base/core/java/android/view/Window.java
|
320742b15a710ede57862eee170945da26ef0172 |
|
23-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
am e3e2883f: am e24a60aa: Merge "First stab at attaching native event dispatching." into gingerbread Merge commit 'e3e2883f2232007174ead562610eb01201890d9b' * commit 'e3e2883f2232007174ead562610eb01201890d9b': First stab at attaching native event dispatching.
|
a95e4cb62f3642cb190d032dbf7dc40d9ecc6973 |
|
19-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
First stab at attaching native event dispatching. Provides the basic infrastructure for a NativeActivity's native code to get an object representing its event stream that can be used to read input events. Still work to do, probably some API changes, and reasonable default key handling (so that for example back will still work). Change-Id: I6db891bc35dc9683181d7708eaed552b955a077e
/frameworks/base/core/java/android/view/Window.java
|
b31e84bc4513e46bac4be8f8d0513f78e360fb11 |
|
09-Jun-2010 |
Dianne Hackborn <hackbod@google.com> |
Add Fragment option menu APIs. Also fix up how transactions are handled so that a series of transactions can correctly be created and committed. Change-Id: I948ba47d49e9b2246a1958bd9eac9dd36dc5a855
/frameworks/base/core/java/android/view/Window.java
|
9b081a809a7e39c6877a9606289ada4680f3d91f |
|
19-May-2010 |
Dianne Hackborn <hackbod@google.com> |
resolved conflicts for merge of 8b625a95 to master Change-Id: I03264c6aad2d87629f9154f5c390cb36ce08efba
|
dc8a7f69d7df5f1ca29763995a0d55acf7936fc6 |
|
10-May-2010 |
Dianne Hackborn <hackbod@google.com> |
Add new API to take over a window's Surface. Change-Id: Iad6245faadc95f19ea63c8e229a1c02e9188f69e
/frameworks/base/core/java/android/view/Window.java
|
33b974393b6fadcefc896ec4a0f9b66724f61e9f |
|
20-Apr-2010 |
Adam Powell <adamp@google.com> |
ActionBar added to framework, integrated with Activity and styles. Added onClick attribute support to menus in MenuInflater. Change-Id: I739771b4f249d87a0d8b15969f3d526b099067a1
/frameworks/base/core/java/android/view/Window.java
|
980a938c1c9a6a5791a8240e5a1e6638ab28dc77 |
|
09-Jan-2010 |
Romain Guy <romainguy@android.com> |
Deprecate fill_parent and introduce match_parent. Bug: #2361749.
/frameworks/base/core/java/android/view/Window.java
|
3be63c09309b21c01b535271625d4c39045690e5 |
|
21-Aug-2009 |
Dianne Hackborn <hackbod@google.com> |
Infrastructure for supporting wallpaper previews. Various things that will allow us to show previews of wallpapers. Also some fixes to animations across wallpapers.
/frameworks/base/core/java/android/view/Window.java
|
6630e4a1dc40850eb7a4ddc8aaa06479469e8c4d |
|
15-Jul-2009 |
Android (Google) Code Review <android-gerrit@google.com> |
am b5c735d3: Merge change 7106 into donut Merge commit 'b5c735d35c8c1d2fb4e4654fbffcdb62d5acab4d' * commit 'b5c735d35c8c1d2fb4e4654fbffcdb62d5acab4d': Return adjusted display for WindowManager.getDefaultDisplay()
|
ddd12535f095d8d056716c3290faf50ec52a538a |
|
14-Jul-2009 |
Mitsuru Oshima <oshima@google.com> |
Return adjusted display for WindowManager.getDefaultDisplay()
/frameworks/base/core/java/android/view/Window.java
|
5b4718ba8aeac969095b75c20fbe74ced0c04725 |
|
02-Jun-2009 |
Mike Reed <reed@google.com> |
make FEATURE_OPENGL public (but hidden for now) so we can test with it
/frameworks/base/core/java/android/view/Window.java
|
c4d5d02667af6989a3121072871f6a4b1e68b594 |
|
22-May-2009 |
Dianne Hackborn <hackbod@google.com> |
Add new window manager type for a hacking second-level media surface. This adds a new window type that is a surface that sits between the current media type and the application window, in theory allowing you to have two surface views in your hierarchy and control their Z-ordering. There is also another hidden API on SurfaceView to set the type of your window. All a big hack, but for the good of the commonwealth!
/frameworks/base/core/java/android/view/Window.java
|
75986cf9bc57ef11ad70f36fb77fbbf5d63af6ec |
|
15-May-2009 |
svetoslavganov <svetoslavganov@google.com> |
Accessibility feature - framework changes (replacing 698, 699, 700, 701 and merging with the latest Donut)
/frameworks/base/core/java/android/view/Window.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/Window.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/Window.java
|
d24b8183b93e781080b2c16c487e60d51c12da31 |
|
11-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@130745
/frameworks/base/core/java/android/view/Window.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/Window.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/view/Window.java
|