This prevents the drop down from resizing when the keyboard is shown / hidden, and thus fixes the issue where the 4th item in the list could not be selected when in landscape mode.
Bug: 2096394
Change-Id: Id0e687c897a724379073dcfa82de7ce89ae12035
This introduces a new activity that you can derive from to implement
a wall paper configuration activity. This is supposed to select
a theme based on whether it is being run to configure a real wallpaper
or a preview, but this is going to be more difficult to do than I
thought. :(
Also fix a problem in the white theme where the list view's background
was being set to white, so it wouldn't work on a transparent bg.
Change-Id: I26d5a8695a3c878a1664eb09900eded57eaff990
This widget is an extension of ImageView that takes care of the standard
fasttrack badging and on-click behavior. It should be used in any
applications that display contact photos.
This view's name will have to be changed before release, and will be
kept private until the name change is made. At that point the view will
be made public api.
Change-Id: I4704e0e979466929ad7b2ef11911681a5028b4a7
This takes care of allowing us to cancel the back button. The
back button is a bear because it is strewn all over the place --
everywhere you can close something, there is some code looking
for the back button that now needs to deal with being canceled.
The main things changed are activity (of course), dialog,
input method, search dialog. There are some other misc places
in the framework (and some I missed here that I will get in a
second pass).
To facility all of this, the key dispatching APIs now provide
a lot more support for dealing with looking for cancelled keys,
and incidentally also provide an actual API for catching long
key presses. This also helped clean up the code in PhoneWindow
where it deals with all of the combinations of key pressed and
releases. (And also allows people to override
Activity.onKeyLongPress() to provide a different long press
action for a standard key like search.)
And while I was doing this, I reworked how we detect long
presses by having this be part of the key event delivered by
the window manager. This should greatly reduce (hopefully
outright eliminate) the problems with long presses being
mis-detected when an application is being slow.
Change-Id: Ia19066b8d588d573df3eee6d96e1c90fdc19f57d
The underlying ProgressBar implementation doesn't know how
to correctly update the thumb graphic, so AbsSeekBar must
call invalidate() at key moments to ensure things look
correct. This bug is one such instance: when you pick your
finger up off the seekbar, the "value" of the progressbar
appears not to change, so ProgressBar feels no compunction
to repaint. AbsSeekBar now invalidate()s on ACTION_UP and
ACTION_CANCEL to ensure that the thumb is correctly drawn.
Also pretend to fix#2054990 (com.android.frameworktest: java.lang.NullPointerException
at android.accessibilityservice.AccessibilityService$IEventListenerWrapper.executeMessage(
AccessibilityService.java:215))... simply by making the variable that apparently was
null final, to assure myself that there is no possible way in the world for it to be
null. :p
Change-Id: I73e337d65b8360721896a0296691257b3e47564b
Use the fact that the scroller keeps track of the current velocity
to accelerate subsequent flings. The current velocity is added to
the new velocity if the flings are in the same general direction
and if the fling animation hasn't been aborted.
This makes it easier to move to the top or bottom of very large
pages (either in overview mode or reading mode) by taking
consecutive flings as a cue from the user that they want to
page faster. The user can stop the fling with any action as
before.
fixes http://b/issue?id=2066090
New tab assets. We decided to do a straight swap and then assess the
damage.
New default dark background color.
New list divider assets.
Change-Id: Ia00a9bb0ee1bad4f955f1c3b5b67526f62572015
Merge commit '36d5aaec2ee1f11ea80639c8194e4aac2be3892d' into eclair
* commit '36d5aaec2ee1f11ea80639c8194e4aac2be3892d':
Add FLAG_ACTIVITY_NEW_TASK flag when adding a word to the dictionary.
mThumbOffset previously defaulted to 0, which caused drawing artifacts at
extrema of very long SeekBars.
The thumb offset can still be overridden by declaring android:thumbOffset in
layout or calling SeekBar.setThumbOffset(int).
Bug: 2064664
support these functions.
This extends the MediaPlayerControl interface with some new methods, and uses
reflection to detect whether the old or new interface is used by an application.
Merge commit '54ba86f0e236a55fb4dc3aabbd81078f586321a5'
* commit '54ba86f0e236a55fb4dc3aabbd81078f586321a5':
Honor the clickable and enabled properties in ListView.
Merge commit '7d68dae99ff2bb3c3aa066efc5b4b1d5c0cd332e'
* commit '7d68dae99ff2bb3c3aa066efc5b4b1d5c0cd332e':
Allow animation styles to be applied to popup windows.
createContextMenuInfo() should have been subtracting any
header views, similar to performItemClick(). Previously,
this caused getUnflattenedPos() to return invalid positions.
This fixes http://b/issue?id=1778239
This unfortunately requires API changes because the existing text markup
classes had no access to the screen density.
TextPaint gains a "density" field so that TextView can pass the density
along. AbsoluteSizeSpan gains a new flag to indicate that its argument
is in dip instead of in physical pixels. LineHeightSpan gains an inner
interface whose chooseHeight() method includes a TextPaint argument so
it can get at the density. And when StringBlock creates the markup
objects, it now uses the density-aware versions.
Bug 1976971, Bug 2031746
Merge commit '4c85f133e10ceaeb2553adb397d4828a7091e7e6'
* commit '4c85f133e10ceaeb2553adb397d4828a7091e7e6':
If no interpolator is specified for a progress bar in the theme, default to a LinearInterpolator.
Merge commit 'a7a3b6ef0fdaf6b17993642b76baf90a03ae0077'
* commit 'a7a3b6ef0fdaf6b17993642b76baf90a03ae0077':
Dismiss both the soft keyboard and the search dialog on back if there is no text entered and no shortcuts are being obscured by the soft keyboard.
This fixes the bug where, in SINGLE_CHOICE_MODE, calling
ListView.setItemChecked(x, false) would always uncheck all
items, even if another item, y, was currently checked.
