Therea re 2 fixes here:
- We sometimes cleared a flag in ViewAncestor too soon that controlled
how invalidated areas were redrawn (related to whether the invalidates
happened on opaque views or not).
- TransitionDrawable was always setting/restoring alpha values on its
drawables every time it was drawn. setAlpha on BitmapDrawable causes
an invalidation, so essentially this was an infinite invalidation/redrawing
loop. The fix was to notice when the animation was done and to simply
draw the appropriate drawable[s].
Change-Id: I1849a5a909b0039a0e9bce0aa3cfc33c50f8f854
Due to the property trigger on persist.sys.usb.config,
setting the default function also sets the current function.
Now we combine both of these methods into setCurrentFunction, which has
a "makeDefault" option to make the new function the default.
This change should eliminate some problems with setting properties due to
multiple property triggers happening at the same time.
Change-Id: I9851299e9c2ee20475eada1a8104c0d50bf5a9e1
Signed-off-by: Mike Lockwood <lockwood@android.com>
Now that landscape on phones uses the config_prefDialogWidth setting
to restrict the default size of dialog windows, the options menu panel
was affected.
Restrict the ratcheting preferred width feature based on the width
LayoutParam only, and respect the LayoutParams width provided by panel
windows.
Change-Id: Idc62f41910f6f22dc50cab978c5642bb0a8dbdaf
Previously we only sent hover to the topmost child, but this doesn't
handle cases where multiple children are overlapped to achieve
certain special effects. Now we send hover to all children until
one of them handles it.
Also moved the call to send the accessibility event into the
main dispatch function so that we can send the accessibility event
for all innermost hovered views even when setHovered() might
not be called.
Change-Id: I6fb8b974db44b594c441deafc012b8415afdfac7
- revert previous fix (transforming >=0 to >0)
- initialize mUserPaddingStart and mUserPaddingEnd to -1 in the specific View(Context context) constructor
- cache mUserPaddingStart and mUserPaddingEnd a bit earlier in View(Context context, AttributeSet attrs, int defStyle) constructor
- cache also mUserPaddingStart and mUserPaddingEnd in setPaddingRelative()
Change-Id: Ibe398da7af35f77655d7006444fa49c9c5387f62
Modified onHoverEvent so that a view only has its state changed to
hovered when the view is clickable. The intent is to prevent labels
from taking hover focus away from their containing view group despite
not being actionable in any way. The child will still receive
a hover event but, if it does not handle the event (returns false),
the hover event will bubble up to its parent and ancestors allowing
them a chance to handle the event instead.
The new onHoverEvent semantics are better because now they closely
mirror those of onTouchEvent. This makes it straightforward to
implement views that respond to hover by changing their visual
appearance (such as by making buttons glow when hovered).
Added onInterceptHoverEvent to enable ViewGroups to explicitly
intercept hover events within their bounds.
Exposed the new hover event API for real.
Change-Id: I63195c8f5c74b859f6047487f9a0f703e8f40ffe
Tainted events should still be processed, even if we don't bother
the developer with the details.
The check for nested calls to the event verifier must incorporate
the event type because different event types might be overridden
in different subclasses so the nesting depths may vary.
Change-Id: If2fb213e07db783a0bd1da97bb12aad93126d712
1. The query string was not converted to lower case during search
for infos with text.
bug:4818098
Change-Id: Ie4ba8ac2632072bdd71070ec8fd24ca255560ac0
1. While mapping Android hover to WebKit mouse events I was not
taking into account the horizontal and vertical scroll.
bug:4807087
Change-Id: Ie24a8a30ce6a20d27b627ae7c7fbff1b74d140c8
1. Updated the code to return empty list instead.
2. Updated the doc to explain that the search is done in the
sub-tree rooted at the info whose method is called.
Change-Id: I560d2563ed4772305bf2d7919560ef19baa30a1d
This adds a Java-language implementation of EventRecurrence.parse(),
to make it easier to relocate it for the benefit of unbundled
Calendar.
Differences from the native version:
- enforces that FREQ appears first
- allows (but ignores) X-* parts
- improved validation on various values
- error messages are more specific
- enforces that only one of UNTIL and COUNT may be present [disabled]
- allows lower-case property and enumeration values [disabled]
As part of the transition process, both versions of the parser are
called on every request, and the results are compared. If the results
are different a warning message is logged.
An unnecessary constructor was removed.
This also this moves some EventRecurrence tests out of CalendarProvider,
into coretests, and adds a simple parse test with the examples from
the RFC.
Bug 4575374
Change-Id: If737ed1272fda65c93363d87b2da12b85e644f5b
Engines must declare a <meta-data> attribute in their
manifest with name "android.speech.tts". This must reference
an XML resource as per
com.android.internal.R.styleable.TextToSpeechEngine.
Change-Id: I56a6b9f1a360174f98c9f39da901ade83d0f38a7
