| Age | Commit message (Collapse) | Author |
|---|
|
This CL adds a new build-library.gradle file for AOSP dialer.
This allows the dialer to be built as a library that can be
included from GoogleDialer.
Switching to a library project meant making two other changes:
- changed all switch statements that used resources to if statements.
This was required because resource IDs are not final in library
projects.
- changed InCalUI code to import com.android.dialer.R instead of
com.android.incallui.R. See http://b.android.com/82743 for more info
on why this is required.
src-N isn't supported yet. Also, this isn't the ideal project layout.
In the future we should consider switching to the following layout:
- dialer/incallui/ <- incall UI as an independent library project
- dialer/dialerlib/ <- dialer code as an independent library project
- dialer/app <- skelent app that builds a standalone dialer AOSP app
Bug: 26676586
Change-Id: I07fbee4d33cc683539e4f8b3953c93f1427af9d7
|
|
An accessibility click on the glowpad now exposes the touch targets
as virtual views to accessibility services. Performing an accessibility
click on each virtual view performs the same function as swiping towards
that target.
Mark contact photo as unimportant for accessibility, it doesn't provide
any useful context or functionality.
Bug: 19075527
Change-Id: I2e980394175bf77379f5cb99126dd5970e0f0555
|
|
If the drawable for the handle changes, a new TargetDrawable is
created (without the correct positional parameters). This causes it
to be misaligned (e.g. during call waiting).
To fix this, simply replace the drawable without creating the TargetDrawable
from scratch. This preserves its positionX and positionY variables.
Bug: 20860087
Change-Id: I696bddf2d6d92cd8f17a3818367e9c0ac71b4a63
|
|
* commit '378453190f85c0ecb0d643a75e781df32ddaa3b2':
Minor UI tweak
|
|
Change-Id: I37c1132d06264c3e8cdbbf181fe274cd26a99c80
|
|
* commit '6676f4e282b0c1166a4fd92c8f0a3c78ac8b37b5':
Remove dependencies on FloatMath
|
|
See frameworks/base commit 33253a4baa6279f81a73425b49dfb6abe5f5416e
for details.
Bug: https://code.google.com/p/android/issues/detail?id=36199
Change-Id: I3e06d3050dc14c2b065ade4fa6a00079c2be735f
|
|
- Refactor code be more flexibile/specific in specifying the targets
for the glow pad; went from "n-way" labeling of different target sets
to more explicit labeling of scenarios, such as "audio without sms".
- Add target sets and cases for showing targest in AnswerFragment.
- Added new drawable for the target to answer a video call.
- Add method to GlowPadView to allow changing the handle (now it may
be either a videocamera or phone icon, depending on the scenario).
- Add a new video handle for incoming video calls.
- TODO: Hook this up to show these glowpads if there is an incoming
video call.
- Deleted some unused resource files.
Bug: 16015750
Change-Id: I77ff08f45f57cd2817866b5d78648af8891bb675
|
|
BUG: 13636003
Change-Id: I28dfcf2506a5dcff6d17990eaf416ea18dada762
|
|
+----------------+
| ---- |
| - - |
| - - |
| - - |
| ---- |
+----------------+
| h | from square edge to circle edge
| d | diameter of circle
| w | width of square
Those are the three values involved in the calculation that we are
changing. The formula calculated the center of the circle (glowpad).
When setting the x position of the glowpad we should always grab the
radius of the circle (d/2) then set h to a proper value depending on
the gravity setting:
left) h = 0 // do not shift at all
center) h = (w - d) / 2 // half the diff. between box and circle widths
right) h = (w - d) // total diff. between box and circle widths
This is what the code does after this change. The flaw that I saw was
that instead of using the radius and adding to h, we used the maximum
between the radius or w/2 (half the width of the box).
The result was that in rare occassion (possibly for the first time in the
associated bug) where the circle is smaller than the box, we would shift
too far to the right because w/2 is always larger than the more
appropriate d/2. I don't know why this was done, but I have added
jaggies@ who originally wrote the code.
I consulted with christinech@ and both determined that this is the
correct mathematical formula.
I verified that the old code did not work correctly for left, right, or
center and that all three work as expected with the new code.
bug:10958942
Change-Id: I781dc25601382d7a43408cbce0badf8a0a90d663
|
|
Bug: 10634748
Change-Id: Iac3d424e7d6be94230da12f3058214b7ca3d8a84
|
|
Along with glow pad for incoming call interaction..
Change-Id: I8d518b5247bee4a10c8fd06763a7e3fe6cff5652
|
