| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
RTL." into ub-launcher3-burnaby
|
| |
| |
| |
| |
| |
| | |
Bug: 21499466
Change-Id: I566cd89dfb855f89f4e68bf56e48bf99204b11ab
|
|\ \
| | |
| | |
| | | |
ub-launcher3-burnaby
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This alters the widget host view code to consider stylus button presses
allowing the user to pick up widgets with a stylus button press, and drop
them by releasing the button.
Bug: 20430722
Change-Id: I359f72bd80016f4b313aab1325cc92d7c6fd2a8c
|
|\ \ \
| |_|/
|/| |
| | | |
press" into ub-launcher3-burnaby
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This updates almost(*) all locations that use a long press listener to
also set a custom touch listener that recognizes the stylus button press
action.
The stylus button press action is: when a stylus touches a view while the
primary stylus button is pressed which may occur on a DOWN or MOVE event.
*The location this is *not* enabled for is: Longpress to enter "overview"
mode -- this isn't really a selection or drag n drop action; it is also
easy to accidentally do this while using the stylus gesture to drag n drop
items which is not an ideal interaction. Also not set for the "cling" that
demonstrates this.
Bug: 20430722
Change-Id: I9343f143261a7b4fada9afca28b8a11a60dbecca
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 21492784
Change-Id: I1b28ac8f44498e1d9770e770b074f19c721c3f10
|
|/ /
| |
| | |
Bug: 21583308
|
| |
| |
| |
| |
| |
| | |
> Make package-private and @Thunk all private methods and constructors accessed from inner classes.
Change-Id: Ie5913860a0c33e48e9bf68f9b5b1699f64c2f174
|
| |
| |
| |
| | |
Change-Id: Ia84445285d013fe8da3c895f5264f329f2403890
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
> Fixing top padding (b/21304523)
> Alinging the label and page indicators to the icons
> Fixing folder label alingment in RTL (b/21445821)
> Updating footer animation (b/21336853)
Bug: 21304523, 21445821, 21336853
Change-Id: I2cf3a48c76653b19437b31252d6ee559ce798094
|
| |
| |
| |
| | |
Change-Id: Ib09df0a3d587dc60ed888ddbd0edf058e4a1cc3e
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This CL adds a Settings activity along with the code needed to provide
a "Allow Rotation" setting to all phones and tablets. This setting is
set to false for phones and true for tablets. On changing the setting
from unlocked to locked, the launcher (and the Settings activity)
will get locked to the orientation the user was in when he disabled
"Allow Rotation". This is consistent with how the natural rotation
feature of Android works.
Change-Id: I8a1c59d1fa0bb9262530cad96e0a9bdbab0d9344
|
| |/
|/|
| |
| |
| | |
Bug: 20222023
Change-Id: I171d75a33694fc2cb347a32cff209f64fe3bf7c3
|
|\ \
| | |
| | |
| | | |
ub-launcher3-burnaby
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 595395d84f0507a1c5c163ad4722fa4345376079.
Change-Id: I44913141f6cb3af29b4509d6b7c317247d1f24c9
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 20222023
Change-Id: I6f6577112845fec14ae2e9c6e88ff3569bd2f1af
|
| | |
| | |
| | |
| | |
| | | |
bug: 21338696
Change-Id: I00d67e53e03e33b26a8eadb669b60fec47553f26
|
|\ \ \
| | | |
| | | |
| | | | |
into ub-launcher3-burnaby
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- removed redundant code to sort the device profiles
- removed DeviceProfileQuery class
- Added a helper method inside the test to easily generate
interpolation graph looks like:
https://docs.google.com/a/google.com/spreadsheets/d/1a1fdemrOqIDixiql77h0anWzUD3GlYfGsbP2FfIhyPM/edit?usp=sharing
Change-Id: Ia4c54a8d59a049c418c08d1b766f07ac6e1d0944
|
|\ \ \ \
| |_|/ /
|/| | |
| | | | |
ub-launcher3-burnaby
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 21445825
Change-Id: Ie43d24ce9c8c08dc2c4b3e24692d497760d8cd2d
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- This change has no effect on actual functionality but to make it easier
for widget tray to inherit the goodness of the 1) fast scroller
functionality 2) unify the scroll look and feel with the all apps view
b/21375339
Change-Id: Ib859b1c3352c0b69f16549ded8f20eb82cf58ba8
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
description." into ub-launcher3-burnaby
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Also defer adding entry to cache until we know that it has correctly loaded
Bug: 21446070
Change-Id: Ia7aae65ecdc5d9d7741f75d3fb6e7b85daeafeff
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
event." into ub-launcher3-burnaby
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Idec0e333a0d3c3a0c232d3e2240f18174e0ea88c
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
vew. The reason for non-scrolling was excluding the pages view from the accessibility hierarchy by marking it as non-important. So, I just removed the code manipulating [non]importance of the PagedView." into ub-launcher3-burnaby
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The reason for non-scrolling was excluding the pages view from the
accessibility hierarchy by marking it as non-important. So, I just
removed the code manipulating [non]importance of the PagedView.
However, this would make the PagesView accessibility-focusable, which is
undesirable. It becomes focusable because it supports long clicks in "normal"
mode. Since it doesn't support accessibility long clicks (i.e. Overview mode is
fetched NOT via accessibility long-click), I just disabled accessibility
long-clickability, which made PageView non-focusable, and it started to behave
correctly.
Bug: 21281859
Change-Id: I7ab01e5f39cb37c456c961199c27458c9bda1c3d
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
> Adding empty page synchronously, instead of waiting for a frame
> Changing launcher state from widgets screen in the same frame, similar to all apps
> Removing DragEnforcer, and moving that logic in side the workspace, disabled by a flag
> Using first page to get page bounds in drag layer, as last page may not have been measured
Change-Id: I172ba4e5ce44648ac55402d49994542c6e10f101
|
|\ \ \ \
| |_|_|/
|/| | |
| | | | |
ub-launcher3-burnaby
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
> This check was used for flushing the cache, but since the cache
is backed by a DB, this has no effect as same icons are loaded again
Change-Id: Ib7d8a8598c5d225d922e095c899dc11ad06f2b7a
|
|\ \ \
| | | |
| | | |
| | | | |
ub-launcher3-burnaby
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
-> The framework circular reveal transition runs on the render
thread which can cause problems when mixed in an AnimatorSet
with transitions that don't run on the render thread
-> See issue 17556455
issue 21445293
Change-Id: Ie19c184c55060651e817d426ec83049b06af56ba
|
| | |
| | |
| | |
| | | |
Change-Id: I2d8ac9a92d2da3d6b0f52ff8a6e3683b05663aec
|
|/ /
| |
| |
| | |
Change-Id: I83c99bb3d3546693200d64e2233957b4c679e7e6
|
|\ \
| | |
| | |
| | | |
into ub-launcher3-burnaby
|
| | |
| | |
| | |
| | |
| | | |
Bug: 20011047
Change-Id: I93cab4e0614b9658b4b657dd98dca68d42580e63
|
| |/
|/|
| |
| | |
Change-Id: Iabafe159a577909396d1602a7eda9c508e95cb71
|
|\ \
| | |
| | |
| | | |
into ub-launcher3-burnaby
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ag/694693
b/21402209
Change-Id: Idae97fca971d90f5fbba658411491147cb023c8d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Renaming resources, dimens, etc to be more consistent
- Removing old AppsCustomize resources and other unused code
Change-Id: I15ce35e7cb7a9b9344fc7103963e4e4c9e45d89a
|
| | |
| | |
| | |
| | | |
Change-Id: Ide9d007adc36b348e19b05cdf49e87f8b02db60e
|
| | |
| | |
| | |
| | |
| | |
| | | |
> Removing workspace_overscroll_drawable_padding which is always 0
Change-Id: I89900738371458a6eb7cbfee215d98b267d6a0b0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
-> Pulling out the parts of device profile which can (and need to be)
initialized and accessed without access to an Activity context,
ie. the invariant bits.
-> The invariant bits are stored in InvariantDeviceProfile which is
initialized statically from LauncherAppState.
-> The DeviceProfile contains the Activity context-dependent bits,
and we will create one of these for each Activity instance, and
this instance is accessed through the Launcher activity.
-> It's possible that we can continue to refactor this such that
all appropriate dimensions can be computed without an Activity
context (by only specifying orientation). This would be an
extension of this CL and allow us to know exactly how launcher
will look in both orientations from any context.
Sets the stage for some improvements around b/19514688
Change-Id: Ia7daccf14d8ca2b9cb340b8780b684769e9f1892
|
|\ \ \ |
|