| ac04f4e69a6de138c5afc668a2c89b7da7ff4e6a |
|
23-Jun-2016 |
John Reck <jreck@google.com> |
Remove FD from the right Looper
Bug: 29586513
Also gives BackdropFrameRenderer a direct-destroy
of Choreographer since it's hammering on new Threads
and we don't want to wait for the GC to release
FDs.
Change-Id: Id2ec0af2ee4d5304961c4ab87a104ccb92f35fc2
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| ca0cf0f52985dd483fe7f59c6b522cfe7c9281e7 |
|
17-May-2016 |
Jorim Jaggi <jjaggi@google.com> |
Fix threading problems with drawables
We can't use the same instance on both the main and the background
thread, as this will lead to problems.
Change-Id: Ieec525f028df2d0596667126d8f5004773461517
Fixes: 28745682
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 0d6222d96d72199f607e3ca5b3d696212372bf47 |
|
19-Apr-2016 |
Jorim Jaggi <jjaggi@google.com> |
Fixes for resize thread
- Make sure to draw navigation bar/status bar background before the
main render node. This is to avoid any flickering when entering
resizing mode, so you rather overdraw than underdraw.
- Draw the first frame from the main thread directly to increase
chance that all drawing commands are processing within a single
frame.
Bug: 27864358
Bug: 28003586
Change-Id: I033f57cdbcb2c16ea93134c041095a415d5c25b4
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 9cd1bbe5c9e14472e631d8cc10005613925f34af |
|
15-Apr-2016 |
Chris Craik <ccraik@google.com> |
Improve multi-window render clipping logic
Fixes: 28125010
Restructures 'scene defer', to implement window backdrop overdraw
avoidance in new render pipeline, and disable clipping to content draw
bounds.
Also restructures FrameBuilder's constructors, to separate out into
multiple defer methods.
Change-Id: I53facb904c1a4a4acc493d8a489921a79a50494e
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| c39c7b0ce2b80fbadfd58245c106cc513b83eac2 |
|
24-Mar-2016 |
Jorim Jaggi <jjaggi@google.com> |
Add shadow during resizing in docked mode
Bug: 27738239
Change-Id: I48c45bd97c2aa7f3d7bbb5b1ba650fbe408bd0bf
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 9511b0f1e9ac629a4a747a0c9373d33ab33cfc32 |
|
30-Jan-2016 |
Jorim Jaggi <jjaggi@google.com> |
Fix bug where surface was not clipped off during resizing
When dragging the divider in a way such the task size goes through
the following transition
- Half size
- Full screen
- Half size
the surface wasn't clipped off anymore. This was because in full
screen configuration, computeDragResizing() == false thus when
going full screen -> half size, we reset the draw state to
DRAW_PENDING to get notified when it has finished drawn. However,
this also broke clipping.
In order to fix this, we always put the window into a resizing mode
no matter whether the bounds are fullscreen or not.
However, this introduces an ugly flickering on the navigation bar,
when going into docked mode, because the app doesn't draw navigation
bar background in resize mode.
To fix that, we calculate the presence of navigation bar whether the
window is fullscreen, and not just whether it's resizing. For that,
we need to calculate the presence in BackdropFrameRenderer, by using
the insets just sent by window manager.
Change-Id: Idf56df4ae7fefe67d068bc2eeda8dc4d83bbefb7
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 0fd2574a1d68b8bfcad0aa8ea68dce60853dfb9f |
|
02-Feb-2016 |
Chong Zhang <chz@google.com> |
Do not draw background if the background drawable is null
Some apps may not have background drawables.
bug: 26729953
Change-Id: I1e93013bb91ba376449bc580646fc733ca4dd072
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| a40fd09fa99fed9526c6603b5af93b7dba259000 |
|
08-Jan-2016 |
Filip Gruszczynski <gruszczy@google.com> |
Load background drawable before passing to backdrop renderer.
Background renderer always expects that the default background drawable
is available. We pass the drawable to the renderer in two places, so we
need to make sure to load the drawable before each.
Bug: 26345599
Change-Id: I238623ff870e26ba34bb02197611172e316d3083
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.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/com/android/internal/policy/BackdropFrameRenderer.java
|
| 04c2fbd6fe389bcfa3a6368d8ae2c20c9e81e4f4 |
|
03-Dec-2015 |
Jorim Jaggi <jjaggi@google.com> |
Draw status bar background in BackgroundFrameRenderer while resizing
To make sure there is always enough contrast between the status bar
icons and the background, we move the drawing for the status bar
background into BackdropFrameRenderer while resizing, so we can
extend the width into the full surface width.
Bug: 24365214
Change-Id: Ifbb10bacf66670c3637f6f6730a8ac47eb1c3939
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 8cc5a74c9049423260a14e0ebb44a052ef8f4e2a |
|
18-Nov-2015 |
Wale Ogunwale <ogunwale@google.com> |
Only add NonClientDecorView when needed
We were previously adding it to all decor views because it was
required to be able to draw the resizing backdrop. We now manage
the resizing backdrop independently of the NonClientDecorView.
Bug: 25082500
Change-Id: Ib786d55eacd221e5d36a4afca9117d5409499674
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| bf9eefc72f7da2048252d96175d04904a9503c57 |
|
17-Nov-2015 |
Wale Ogunwale <ogunwale@google.com> |
Move management of BackdropFrameRenderer to DecorView
Allows us to have the BackdropFrameRenderer independent of having
a NonClientDecorView.
Bug: 24810450
Change-Id: Ibcda3d722970536ee037b192e90e01da5650ac74
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|
| 0b3562db3e01abce88f20bf2faeba61cce00d438 |
|
17-Nov-2015 |
Wale Ogunwale <ogunwale@google.com> |
Moved BackdropFrameRenderer from NonClientDecorView to its own class file
Bug: 24810450
Change-Id: Id86e97733161499bbc59617433792f5ddc4e7f9e
/frameworks/base/core/java/com/android/internal/policy/BackdropFrameRenderer.java
|