Now the IME is hiddedn once the user starts flinging since he is
using another method of updating the current value. This is now
consistent with the case of shown IME and poking the up/down
button.
bug:5174339
Change-Id: Id25934f394314a285b753f0bec7f422034ada90a
- Don't try to create a thumbnail bitmap on the client side. This
wastes 64k, and isn't needed since we are doing screenshots.
- Optimize View to put all of the callback pointers out of line.
Added a couple new APIs so these don't need to be protected/public.
- Lazily create ViewGroup's cache paint.
- Change FrameworkPerf app to not use HW accel drawing, to give better
comparison with GB.
Change-Id: Iec56d02459820d74a4cc9c7ec9c1856563c82c7b
1. Now the NumberPicker has minWidth/minHeight that is the lower bound
of the correspodning size for which the widget looks well enough to
be usable. There is also maxWidth/masHeight that is the upper bound
of the corresponding size for which the widget looks best. The picker
tries to greedily reach the max dimesions for which it looks best.
2. The NumberPicker was not taking care of the max width of the items
is shows numbers/strings mapped to numbers. Now if not explicitly
specified the widget computes the maxWidth at which it looks best
based on the content it shows.
3. Removed an unnecessary layout for number picker on tablets.
4. Updated the TimePicker/DatePicker to not hard-code width for the
number pickers it uses, rahter wrap the content.
bug:5417100
Change-Id: I432aa96185961e59a058a2565b15265ba7394818
Tweak to the logic to take account of margins when gravity = FILL is used and
there is a measurement dependency between the axes (as in mulit-line text).
Cherry pick ecab117864 to MR1
Change-Id: Ic0c95a4618bdb32acca75219796c66c1fc467610
SpellChecker is exclusively called from the main UI thread and
there are no concurrency issues. As a result, the TextView's
wordIterator can safely be re-used in the parse() method.
Also reset the pool of SpellParsers on language change.
Change-Id: I1cc8a2750f21233754f006e40a81622730030ec8
In Recents in landscape, we were seeing blue flashes when scrolling; generally, almost every scrolling container should be delaying child presses to prevent this problem
A recent patch taking scroll into account was applied at the wrong
level. isVisible() expects positions that already take scroll into
account. isOffsetVisible() is where the initial bug was.
Cherry pick of 144415 from master.
Change-Id: I06ceebfb3d7b24aa4adba886c24fcf9d8dd39d2e
This reverts commit d224c88c48.
Based on Dianne's comments, this small optimization seems uncessarily
risky. I'll submit a new change where each SpellParser has its own
WordIterator to make this thread-safe.
Change-Id: Ic09fa656b00d284536e58f4cc7d26d5e26c3f3cf
Measuring line widths, glyph by glyph slows down the scrolling
process for long text (for some reason, width measure efficiency
is affectedi by text length, maybe because the whole text has to
be passed to JNI layers).
This optimization avoids this computation in the case where there
is no possible horizontal scroll.
Change-Id: I2082e3d0eedace1a86122a03e4b21f90f3bc8522
Limit each parse to batches of a few words, to keep the UI thread
responsive.
Possible optimizations for the future:
- SpellCheck in a thread, but that requires some locking mecanism
- Only spell check what is visible on screen. Will require additional
spans to tag the pieces of text.
Change-Id: Ibf8e98274bda84b7176aac181ff267fc1f1fa4cb
1. Now the NumberPicker has a max height and width for which is looks
good but can still shrink if there is not enough available space.
bug:5512787
Change-Id: Ieea88cafa8408e1d4160bab4bfe2b771bd79f7f8
