| 588e117cce8d9a7a2a763713cecc3b0fa44e8031 |
|
04-Sep-2014 |
Svetoslav Ganov <svetoslavganov@google.com> |
This is no longer needed for factory ROM and since it changes behavior - reverting. Also causes NPE crash.
Revert "NumberPicker not announcing current selection."
This reverts commit 44d026c95bb9e582b7b18e355ec7a3458df52259.
Change-Id: I0bb6db9666fc9eb477737d1114c5c87035ed202b
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| ca505661010cae519408b3cc96e18e6c95339bd0 |
|
03-Sep-2014 |
Svetoslav <svetoslavganov@google.com> |
NumberPicker not announcing current selection.
bug:17299486
Change-Id: I73fd33ef3518ef8e6cdd40cd036e8f104dc492b6
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 9eef3f4fb92d4abd4e217c13cdf72bd4fc3e59f2 |
|
23-Jun-2014 |
Craig Stout <cstout@google.com> |
NumberPicker fixes for Android TV.
Fixed stuck dpad navigation when end of range is reached.
Adds theme attribute 'hideWheelUntilFocused'.
b/15194230
Change-Id: I9a77c6ad29a1fd930a8920d9944ad1eb15ca6b96
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| f8d4602c9bd7dc163323368beb8db23f5a8fe36b |
|
03-Jul-2014 |
Brian Duff <bduff@google.com> |
am 51d70ce9: am c542745e: am a6e9dd3f: Merge "Fix a typo in NumberPicker javadoc."
* commit '51d70ce9b8dbbcb7f354c87b722efe84b2a62a28':
Fix a typo in NumberPicker javadoc.
|
| 51d70ce9b8dbbcb7f354c87b722efe84b2a62a28 |
|
03-Jul-2014 |
Brian Duff <bduff@google.com> |
am c542745e: am a6e9dd3f: Merge "Fix a typo in NumberPicker javadoc."
* commit 'c542745e23fe9d2e71c1f607d66f5570f585133d':
Fix a typo in NumberPicker javadoc.
|
| a6e9dd3f9a2d966faf2d1710d2189127b968dc52 |
|
03-Jul-2014 |
Brian Duff <bduff@google.com> |
Merge "Fix a typo in NumberPicker javadoc."
|
| 1f2966ea2bd001adde9ee4773d97d1bb6007aa53 |
|
11-Apr-2014 |
Elliott Hughes <enh@google.com> |
am 8e6992fb: am 1ea1857d: am 8cd319b8: Merge "Add additional languages to be accepted by the NumberPicker input filter"
* commit '8e6992fb3ac986d3bbb93cd2d55d3e18eb03b3b5':
Add additional languages to be accepted by the NumberPicker input filter
|
| 8e6992fb3ac986d3bbb93cd2d55d3e18eb03b3b5 |
|
11-Apr-2014 |
Elliott Hughes <enh@google.com> |
am 1ea1857d: am 8cd319b8: Merge "Add additional languages to be accepted by the NumberPicker input filter"
* commit '1ea1857de9c98199015f0188678a12a82a6248d4':
Add additional languages to be accepted by the NumberPicker input filter
|
| 1caa092f94aaa4b9b7b382263dfd13581d92d2de |
|
04-Mar-2014 |
Svetoslav <svetoslavganov@google.com> |
Allow click listener registration in NumberPicker.
NumberPicker is composed of three areas, increment, decrement, and value,
which take the entire space. Hence, adding a click listener was a no-op.
Clicking on the value brings up the IME but for devices with very small
screens a developer may want to override this default behavior to say
confirm the selection.
This change allows adding a click listener to NumberPicker to override the
behavior of clicking on the current value. This is applicable only to the
new look and feel of the NumberPicker, i.e. the holo themes. This change
is safe as previously setting a click listener had no effect.
bug:13287234
Change-Id: I34e12a2e2bd64344a4797153fa6c820001a4722e
(cherry picked from commit 46a27efe9528ac3c5b37726707844e7c868815ac)
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 46a27efe9528ac3c5b37726707844e7c868815ac |
|
04-Mar-2014 |
Svetoslav <svetoslavganov@google.com> |
Allow click listener registration in NumberPicker.
NumberPicker is composed of three areas, increment, decrement, and value,
which take the entire space. Hence, adding a click listener was a no-op.
Clicking on the value brings up the IME but for devices with very small
screens a developer may want to override this default behavior to say
confirm the selection.
This change allows adding a click listener to NumberPicker to override the
behavior of clicking on the current value. This is applicable only to the
new look and feel of the NumberPicker, i.e. the holo themes. This change
is safe as previously setting a click listener had no effect.
bug:13287234
Change-Id: I34e12a2e2bd64344a4797153fa6c820001a4722e
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 962dde734b7e347948a1624571e8c180260bae85 |
|
05-Jul-2013 |
Martin Olsson 4 <martin4.olsson@sonymobile.com> |
Add additional languages to be accepted by the NumberPicker input filter
Adds Devanagari, Bengali and Kannada numerals to be accepted by the
input text filter of the NumberPicker class. Before this patch only
Latin and Arabic-Indic numerals was accepted as input.
Change-Id: I82a7e88e09c894ee55ef301d109e3d6b867c6ff6
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 7f67d7206af0b0990c410547b34f5672ca93b44c |
|
19-Sep-2013 |
Alan Viverette <alanv@google.com> |
am 8ac0d137: am 564c45b9: Merge "Fix number picker vertical scroll computations" into klp-dev
* commit '8ac0d137ba11958312e25225d8d0776aad71b022':
Fix number picker vertical scroll computations
|
| fd63917ed31fbf425362d209eff72d5e64c5bb8a |
|
18-Sep-2013 |
Alan Viverette <alanv@google.com> |
Fix number picker vertical scroll computations
BUG: 8692209
Change-Id: I332d3f1c00e1aacad11f8af172974741b28843ea
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| c2cbd9cbada0240a84993f397c2804a176f7d66e |
|
18-Sep-2013 |
Alan Viverette <alanv@google.com> |
am 9ac68dc6: am 84c5ade8: Merge "Fix vertical scroll computation in NumberPicker" into klp-dev
* commit '9ac68dc69ffe0104dd098ad14a8a8b103ca8b09e':
Fix vertical scroll computation in NumberPicker
|
| 5ba99f58b1e90a6faaf5e84d713e10cf0323ac96 |
|
13-Sep-2013 |
Alan Viverette <alanv@google.com> |
Fix vertical scroll computation in NumberPicker
BUG: 8692209
Change-Id: I3f0a36abde7987a72d1470307c55db9b70cb5ab2
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| d9273d6f289d9b55da3fd0db2f659fdfb48106a8 |
|
31-May-2013 |
Tor Norbye <tnorbye@google.com> |
Add typedefs and nullness annotations.
This changeset adds in typedef annotations (custom annotations
marked with @IntDef) for various int parameters and return values
in the API. It also adds nullness annotations for cases where the
documentation explicitly mentioned null policy, or where it was
blindingly obvious from the context. Also fixed some typos in the
documentation.
Change-Id: Ica27c01368895818e26237544edd8483007155bb
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 617feb99a06e7ffb3894e86a286bf30e085f321a |
|
10-Sep-2013 |
Alan Viverette <alanv@google.com> |
Add View constructor that supplies a default style resource
Also updates the constructor of every class that extends View.
BUG: 10676369
Change-Id: Ifaf27bf82028d180afa4931c0e906df88d858ac3
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 0db4c3e0ed0e9a85f11db41285b9adb000c3f211 |
|
08-Sep-2013 |
Brian Duff <bduff@google.com> |
Fix a typo in NumberPicker javadoc.
Change-Id: I7c1777e166dabe2e24403301049f2d6e06b97e2d
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 46bfc4811094e5b1e3196246e457d4c6b58332ec |
|
17-Aug-2013 |
Romain Guy <romainguy@google.com> |
Fix hardware layers lifecycle
Bug #10075732
Hardware layers could survive across EGL terminate events.
Change-Id: Ie8565d55cb29fe6625fa1584d695edfecd37ab5e
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| dbed27e5e431d59142d11c552f7f13483658c35d |
|
24-May-2013 |
Alan Viverette <alanv@google.com> |
DO NOT MERGE. Fix number picker accessibility focus.
The node bounds populated by the child TextView were not consistent
with the bounds manually populated for its parent NumberPicker.
Bug: 9072003
Change-Id: Icbfa64f52cf11fd39c7243936227b8ba36280c3c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 0e2d281083e375d3b0bd44d61dbbef5c6d93921e |
|
22-May-2013 |
Alan Viverette <alanv@google.com> |
Fix number picker accessibility focus.
The node bounds populated by the child TextView were not consistent
with the bounds manually populated for its parent NumberPicker.
Bug: 9072003
Change-Id: Icbfa64f52cf11fd39c7243936227b8ba36280c3c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 6d8a99fecc5dd3aec502c0419af61e8d2a3c398d |
|
25-Jan-2013 |
Sungmin Choi <sungmin.choi@lge.com> |
avoid multiple-"0" to exceed the length of upper bound
Limits number of "0"s not to exceed length of maximum number allowed
for the NumberPicker.
Steps to reproduce:
1. Settings -> Date & time -> uncheck "Automatic date & time"
2. Select "Set time"
3. Select Time Area on Set time dialog
4. insert 00000000 via NumberPicker
Bug: 8073759
Change-Id: I0f3f5303d9a4b559217adb436f244407a23e58c0
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 5132d62600484bb4fce86295b288c782bee91de8 |
|
27-Nov-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Merge jb-mr1-dev into aosp/master - do not merge
Change-Id: Iee4af268c5c2930c59ee237e796467d79cedbbfc
|
| 7018cfdc05dc6135949806749ff5c370dce09ced |
|
19-Nov-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Revert "NumberPicker should adjust min and max when displayed values are set." (a.k.a. Santa is back)
This reverted change was adjusting the min and max values for the NumberPicker
which is not desirable since it changes behavior and it will be possible for
an app that works on the current platform to crash on an older one. Also the
adjustment was not implemented correctly.
Updated the documentation to clarify the reltionship between the min value,
max value, and the displayed values array.
Bug:7518172
This reverts commit a1410e6789ce72bc423793315a51aea8b6bad6c7
Change-Id: I109f1b1f54c1e609941243cabab9241871b6b12b
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 86cf0cdfe14ce9606d42671b2961081f3220a789 |
|
08-Oct-2012 |
Justin Mattson <jmatt@google.com> |
Reverse movement direction of DPAD events
The first way I had it produces somewhat unexpected behavior. If you
scroll past the top of the list, focus moves down to the control
below.
This changes it so scrolling past the bottom of the list moves focus
to the next control below.
Change-Id: I886e1854df85ceb203dac61c7f8c7daf6749e90e
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 5dc21d9b340fe2c1cb4c37435d8a29429cf3f79e |
|
08-Oct-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding support to NumberPicker
Change-Id: I471b995c8d364c2bd5eef3ab0397c17fc77f6ccc
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a1410e6789ce72bc423793315a51aea8b6bad6c7 |
|
28-Sep-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker should adjust min and max when displayed values are set.
1. The BumberPicker exposes APIs for settings displayed values for the
selected numbers. If the min and max value of the picker are less then
the length of the new displayed values array, i.e. they are out of
bounds, the NumberPicker crashes.
bug:7254000
Change-Id: I182e30216ef28c98d6541f9c985b43c8179dec76
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a65fe884d1bba4c64b961df27bd04e33e28a7209 |
|
23-Sep-2012 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix the build
Change-Id: Ia021742fb33671f9ece48180789757297fa60001
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| d88e3054d08b1f821bb2e27b2647aa16a60d8742 |
|
21-Sep-2012 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix bug #7206086 NumberPicker widget should use locale digits
- fix for having the TwoDigitFormatter being able to be recreated if the locale is changed
- accept now also the Arabic and Persian digits
Change-Id: Ifbf7e274d971008f4a5782402d4b76d9472b68fc
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a90927629881f0faf54c1003ebd38c27a730045e |
|
07-Sep-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding accessibility check in the node provider of NumberPicker.
1. The node provide in number picker was sending accessibility events
without checking whether accessibility is enabled leading to a
crash if accessibility is disable when the event is sent.
bug:7095330
Change-Id: I2e14b757003b4db58922cf6e20ea8e119770e567
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 9dc2cc53ac332d73376f64cc8e7c713762d74bdd |
|
04-Jul-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "AccessibilityNodeInfo bounds in screen incorrect if application scale not one."
|
| 983119ab22a18c743e4084dff27f35e3f490dd34 |
|
04-Jul-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityNodeInfo bounds in screen incorrect if application scale not one.
1. If the application does not accommodate different screen density the
system applies an application scale equal to the device density over
the a default density. The AccessibilityNodeInfo coordinates were not
reported after applying the compatibility scale, therefore the bounds
in parent and screen were not as perceived by the user.
bug:6764586
Change-Id: Iae2d6ea81049364194c7cb09df2240b5eda3d939
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 27e2da7c171afa39358bbead18fbe3e6b8ea6637 |
|
03-Jul-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Remove the accessibility focus search code.
1. In JellyBean we have added some APIs to search for next accessibility
focus in various directions and set accessibility focus from hover.
However, we have decided that there is not clean answer for how this
should behave and the APIs were hidden. Now the accessibility service
is responsible for that. The unused code is now taken out.
2. This patch also takes out the hidden attribute accessibiligyFocusable
since we moved the responsibility for implementing focus search strategy
to accessibility services and we did not need that for Jellybean which
is a good sign that this is not needed. I general this is one less thing
for an app developer to worry about. We can add this if needed later.
bug:6773816
Change-Id: I0c858d72c93a2b7ff1f8f35a08d33ec4b9eb85fd
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a90e4512ab81dcd8cdbefdd2ffa0de55fca1caa3 |
|
02-Jun-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Calling the correct method when adding accessibility focusables.
1. Since we added explicit accessibility focusable attribute when
adding focusables views that do so should call this method. Some
views were not updated to do so.
bug:6581924
Change-Id: Id64c0b2d76e5269ebf3fbe17203e73b174bdb843
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| e54c5f13652166c5896ccfa55f047301a6c8b876 |
|
17-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "Exposing some accessiblity actions only for enabled views." into jb-dev
|
| fb1e80a247221ee7e8f5c5deba04812021d9d07e |
|
17-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Exposing some accessiblity actions only for enabled views.
1. Some accessibility actions should not be performed on disabled
views. For example, scrolling should not be permitted while
accessibility focus should be. Made a quick pass over the
actions we expose now.
Change-Id: I36626dfbc0d2f480309a910f58f1de64e9e05675
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4528b4e882584745f48263fa6626987e63832a2a |
|
16-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Prefetching of accessibility node infos getting incorrect views.
1. The prefetcher of accessibility nodes infos was not folloing
the childForAccessibility relationship when finding the views
whose node infos to prefetch.
2. NumberPicker was not reporting the correct parent.
bug:6471710
Change-Id: Ia7ad5dd031fb4b3816dfe630d5212201cfafa236
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 48d1586f4065fc9ab97a679da1e4f7c327c943f2 |
|
15-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Add accessibility scroll support to some widgets.
1. Added support for accessibility scroll action to
some widgets that are scrollable.
2. Making the super call when handling an accessibility
action in the views to call super first to allow
an accessibility delegate to intercept the call.
bug:5932640
Change-Id: I5eb37d64bf9fba1d5c596981132e0df717e2a18a
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 791fd31a68c59395952005886ba799169f80a29a |
|
15-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility focus traversal in virtual nodes.
1. Finished the implementation of support for maintaining
accessibility focus in view with virtual descendants.
2. Finished the NumberPicker implementation of virtual
subtree such that all requred attributes are reported
and ensuring that it support accessibility focus in
its virtual descentants.
3. Fixed a bug where if a predecessor of the view that is
accessiiblity focused is removed the accessibliity focus
host in ViewRootImpl is not cleared leading to a crash
when trying to draw the accessibility focus highlight.:
bug:6472646
bug:6433864
Change-Id: I3645642b87b4a26025c0b2ba9dfaad92d11a48f1
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 0d607fbe546ac943de38dad33ae681b09efec6ea |
|
12-May-2012 |
Guang Zhu <guangzhu@google.com> |
accessibility bug fix in NumberPicker
* moved View#isVisibleToUser to protected with @hide
* added a new View#isVisibleToUser(Rect), so that a portion of
the view can be tested for visibility
* NumberPicker will report its concrete class name
* code to append virtual children was at wrong place
* boundInScreen for increment and decrement buttons are reported
wrong
Change-Id: Ic5d644b3e1efa15b1f0537907c8cdd4ce43a97c1
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 232dd3f335b8995cd9ab220f7b3fad77076de42b |
|
25-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Polish the NumberPicker, TimePicker, and DatePicker based on UX request.
1. Now the spinners in the time and data picker a wider therefore
easier to interact with, i.e. harder to miss accidentall.
2. Removed the scroll distance cut off user to distinguish between
fling and change by one.
3. Added visual feedback when the areas the serve as virtual buttons
in number picker are poked.
4. Removed the coeffcient that was making drap not to be one-to-one
with the scrolled distance.
5. Added some margin at the top and bottom of the spinners in
date and time pickers.
bug:6321432
Change-Id: I311c1733d1951b0563209401faa830ca70ec87cb
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| aa780c110922148a6a4ba06734bb2b0bb8c98f93 |
|
20-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding support for traversing the content of a node info at granularity.
1. A view that creates an accessibility node info may add to the info
a list of granularity labels. These are granularities by which the
source view can iterate over its content. For example a text view
may support character, word link while a web view may additionally
support buttons, tables, etc. There are actions on accessibility
node info to go to the next/previous at a given granularity which
is passesed as an argument.
2. Added Bundle argument to the APIs for performing accessibility
actions. This is generic and extensible.
bug:5932640
Change-Id: I328cbbb4cddfdee082ab2a8b7ff1bd7477d8d6f9
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4213804541a8b05cd0587b138a2fd9a3b7fd9350 |
|
20-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility focus - framework
Usefulness: Keep track of the current user location in the screen when
traversing the it. Enabling structural and directional
navigation over all elements on the screen. This enables
blind users that know the application layout to efficiently
locate desired elements as opposed to try touch exploring the
region where the the element should be - very tedious.
Rationale: There are two ways to implement accessibility focus One is
to let accessibility services keep track of it since they
have access to the screen content, and another to let the view
hierarchy keep track of it. While the first approach would
require almost no work on our part it poses several challenges
which make it a sub-optimal choice. Having the accessibility focus
in the accessibility service would require that service to scrape
the window content every time it changes to sync the view tree
state and the accessibility focus location. Pretty much the service
will have to keep an off screen model of the screen content. This
could be quite challenging to get right and would incur performance
cost for the multiple IPCs to repeatedly fetch the screen content.
Further, keeping virtual accessibility focus (i.e. in the service)
would require sync of the input and accessibility focus. This could
be challenging to implement right as well. Also, having an unlimited
number of accessibility services we cannot guarantee that they will
have a proper implementation, if any, to allow users to perform structural
navigation of the screen content. Assuming two accessibility
services implement structural navigation via accessibility focus,
there is not guarantee that they will behave similarly by default,
i.e. provide some standard way to navigate the screen content.
Also feedback from experienced accessibility researchers, specifically
T.V Raman, provides evidence that having virtual accessibility focus
creates many issues and it is very hard to get right.
Therefore, keeping accessibility focus in the system will avoid
keeping an off-screen model in accessibility services, it will always
be in sync with the state of the view hierarchy and the input focus.
Also this will allow having a default behavior for traversing the
screen via this accessibility focus that is consistent in all
accessibility services. We provide accessibility services with APIs to
override this behavior but all of them will perform screen traversal
in a consistent way by default.
Behavior: If accessibility is enabled the accessibility focus is the leading one
and the input follows it. Putting accessibility focus on a view moves
the input focus there. Clearing the accessibility focus of a view, clears
the input focus of this view. If accessibility focus is on a view that
cannot take input focus, then no other view should have input focus.
In accessibility mode we initially give accessibility focus to the topmost
view and no view has input focus. This ensures consistent behavior accross
all apps. Note that accessibility focus can move hierarchically in the
view tree and having it at the root is better than putting it where the
input focus would be - at the first input focusable which could be at
an arbitrary depth in the view tree. By default not all views are reported
for accessibility, only the important ones. A view may be explicitly labeled
as important or not for accessibility, or the system determines which one
is such - default. Important views for accessibility are all views that are
not dumb layout managers used only to arrange their chidren. Since the same
content arrangement can be obtained via different combintation of layout
managers, such managers cannot be used to reliably determine the application
structure. For example, a user should see a list as a list view with several
list items and each list item as a text view and a button as opposed to seeing
all the layout managers used to arrange the list item's content.
By default only important for accessibility views are regared for accessibility
purposes. View not regarded for accessibility neither fire accessibility events,
nor are reported being on the screen. An accessibility service may request the
system to regard all views. If the target SDK of an accessibility services is
less than JellyBean, then all views are regarded for accessibility.
Note that an accessibility service that requires all view to be ragarded for
accessibility may put accessibility focus on any view. Hence, it may implement
any navigational paradigm if desired. Especially considering the fact that
the system is detecting some standard gestures and delegates their processing
to an accessibility service. The default implementation of an accessibility
services performs the defualt navigation.
bug:5932640
bug:5605641
Change-Id: Ieac461d480579d706a847b9325720cb254736ebe
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| bc896be574abf1ea92fcefb36ed80390d2366365 |
|
13-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "NumberPicker not redrawn when current value is changed via an IME."
|
| fac14f9731ce7fc765de582c983af751aab697de |
|
13-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker not redrawn when current value is changed via an IME.
1. The NumberPicker scroll wheel was not updated upon value change
via an IME as well as the picker was not redraws after the change.
bug:6291879
Change-Id: I5ba30df42e38cd06fa150328399eb4deeb0b683d
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4a5af365af41fcd759e6480c45166817c6e7bd3e |
|
13-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "NumberPicker cannot fling in scrollable containers."
|
| 83dc45c65988e9b86e156d59f59ede48195ed1d5 |
|
13-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker cannot fling in scrollable containers.
1. NumberPicker was not preventing its predecessor from
intercepting touch events that are on top of it, hence
it was not flingable in scrollable containres.
bug:5661117
Change-Id: I145f59b069f479935f551bc5e841f13468a6c676
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| f7c83bc4d3e1996b491824902a6a0f98ac69bede |
|
13-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker truncates the edited value.
1. NumberPicker aims to reach the specified max width and height.
If the max width was not specified, the picker computes it by
measuring the widest value it will show. However, the case for
recognizing whether the max width is specified incorrect, hence
the max width was never measured.
bug:6193549
Change-Id: If67352a651e8d4a1d060868c876316e1c0e9bd0b
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| fe41ce4ef97e7da585fdbf06988da8047e72b9f6 |
|
03-Apr-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Polish the Number/Date/Pickers per UX request.
1. Now the NumberPicker max height is a bit smaller.
2. The Time/Date picker add top and bottom margin to
compensate for the shorter NumberPickers.
3. The Time/DatePicker dialogs have only "Done" button
and tapping onside saves the current state.
bug:6277808
Change-Id: I4c5928debb1c3b7fe126d6cd6745e3c5eb980901
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| d11e6151fe88314505fa7adca6278de2e772b11c |
|
20-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Revamp of the NumberPicker widget.
1. The number picker no longer shows up and down arrows, it
has only three touch targets which are the currently selected number
in the middle with a lesser one above and greater below, now what
you touch is what you get, flingability and long press are still
supported.
2. Removed the restriction for a View with an AccessibilityNodeProvider
to not have any concrete children. If the View has a provider, then
this provider is responsible for creating the AccessibilityNodeInfos
for all its descendants, concrete and virtual. The number picker is
a good example for such a case - it has a concrete input view and
two virtual buttons as its children. This is a safe change since
this behavior has not been released.
3. This patch also fixes bug where the number picker is stretched too
much in the Theme theme.
bug:6177794
bug:5728294
Change-Id: I5fb370fe0b864a156f5f2aaf2de5f55f6b6d4e84
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| e8331bd2e7ad3d62140143cafba3ff69be028557 |
|
03-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Sync of the NumberPicker attributes with the public Java APIs
1. Renamed some attributes to not overlap with already public
ones since they are not dedicated for external use.
bug:6094713
bug:6104108
Change-Id: Iab8a906680ebcaa91f020ffbf55cf603a1071437
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 69db4df48713d695e40144833c7008020e0720f0 |
|
28-Feb-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
am 0c96daa5: am 0c7ffac4: am a2b41b43: NumberPicker showing IME when its input field gains focus.
* commit '0c96daa5d5a1ef778ad1ef4619ef1fa4c30519c6':
NumberPicker showing IME when its input field gains focus.
|
| a2b41b438d45570867e4682c0caaf93ace5e712e |
|
28-Feb-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker showing IME when its input field gains focus.
1. The NumberPicker was showing the IME if the input field
gets focus and hiding it when the the arrows are pressed.
The leads to a nasty behavior when the input is the first
focusable and the uses presser an arrow button. In such
a case the IME shows and hides on every arrow press pushing
the window content up and down - this looks pretty ugly.
Now the IME is show on double tap of the input field.
2. The NumberPicker input now by default has an IME action
done, hence after editing it the IME goes away.
3. The NumberPicker input now clears focus when it gets
IME action done, so the last picker in a sequence
does not show selection which is focus driven.
4. NumberPicker was incorrectly detecting double tap to
begin edit and it was possble to start edit on singe tap
if the user has double tapped before to start an edit.
Now double tap detection is using the double tap timeout
correctly.
bug:6071977
Change-Id: I0ff5a491064e51663b3abec675d839d0a65b986a
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 0aa8f3b8db3eb97f53dc7fe8f09d5b983300417c |
|
31-Jan-2012 |
Scott Main <smain@google.com> |
resolved conflicts for merge of 20d06540 to master
Change-Id: I80da9a11b4538c070b0000cfa3ea6cd865e46aef
|
| 644053466018c08e326787b909a76355bad1dd30 |
|
31-Jan-2012 |
Scott Main <smain@google.com> |
docs: fix typos and clarify some grammar in summary
external issue 21548
Change-Id: Ic38921cb64390b42651f3971efeb4b76101dfc14
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 3ad774667d33524d2d6d1472ded15f2c6d6f541d |
|
25-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "Fixing a typo in the NumberPicker documentation."
|
| 08a9e9f20abebf3ba47139dd225da1d0fef8ee84 |
|
24-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Fixing a typo in the NumberPicker documentation.
Change-Id: I3a76923d468ddd01cd1ed5521992479cee82c6f0
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 3f9c9eab7b41c409c3c7b503b89ad340e408b6a0 |
|
24-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker should not throw an exception if no enough values for wrapping.
1. The selector wheel was throwing an exception if a client requires that it
wraps its selector wheel if the number of values is less that the number
of values shown in the wheel. While wrapping makes no sense if the all
possible values are already shown, we should not throw an exception,
rather to ignore the request.
bug:5911190
Change-Id: Icd90cd39f66d9f39939801752bf1eb1eef8fe757
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 8a78fd4d9572dff95432fcc4ba0e87563415b728 |
|
17-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityEvent/AccessibilityNodeInfo class name property should be set to only framework classes.
AccessibilityEvent and AccessibilityNodeInfo have a property className which is set to the source
Java class. This is problematic since leads to leaking private classes which would allow an
accessibility service to load classes from other packages. This is strongly undesirable since
not trusted code can be loaded, and hence executed, in the accessibility service. To address
that the class name is set to the most concrete framework class extended by the info/event
source.
bug:5878943
Change-Id: I7b3114ece8772ea2773f5151e21b8a6f2006882a
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 47730f1582dfa67909293d6d5b88ff89c5ad6ed5 |
|
10-Dec-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
am 33a3b2ce: am 48b428fb: Merge "NumberPicker getting stuck if scroll wheel not wrapable." into ics-mr1
* commit '33a3b2cecf174cb14097498214131fcfb32ec04c':
NumberPicker getting stuck if scroll wheel not wrapable.
|
| 234484a9fb53786aa8b7ed2a3df7e24d41817689 |
|
08-Dec-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker getting stuck if scroll wheel not wrapable.
1. If the number picker was not wrapping the selector wheel
it was incorrectly initializing the fling scroller and
the error was proportional to the difference of the
current value and the max size. As a result if the number
picker gets stuck for a very long time.
2. The alpha of the selector wheel paint was not reset on
every subsequent fling so if the wheel was fading out
and a new fling is performed the selector wheel is
dimmed during the fling, rather bright.
bug:5728363
Change-Id: Ia90a6af86f162bda1b28f43f7ba7e4a9f5051b78
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| ddd51fdb7117a6a0812968a47b43067d3d899991 |
|
30-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
am 4661a05b: am 2f504d9e: Merge "NumberPicker incorrectly shown for the old theme." into ics-mr1
* commit '4661a05bef8c98b18698202c758067ac9c965f77':
NumberPicker incorrectly shown for the old theme.
|
| 9f086d812ff04703de4b14e02a7702ba7c8acb33 |
|
30-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker incorrectly shown for the old theme.
1. NumberPicker is trying to greedily grow to its max size
but if the max size is not specified the default value
was the max integer which makes the widget get quite
tall in some cases. Now the widget tries to reach the
max size only if it has been specified.
2. NumberPicker was not computing its min width when the array
of display values is set.
3. DatePicker' layout for the old Theme was adding a margin on
the right of the group of spinners and if the calendar view
is not shown the spinners were not centered. Added the spinners
right margin to the left margin of the calendar view.
4. TimePickerDialog was using the wrong conext and was not dismissable
on an outside touch. Same for the DatePickerDialog context.
bug:5646161
Change-Id: Ic15f9b3e6291b76493604230ceb4f783a04d4ac7
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 1002b622434cff2bd1cbdd96bbe25769de5438fa |
|
09-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
am cc03abe1: am 1bef480b: Merge "NumberPicker incorectly enforcing minimal width and height." into ics-mr1
* commit 'cc03abe1fc51a62e65f22944c3a4cba5dd3c34d3':
NumberPicker incorectly enforcing minimal width and height.
|
| 698e1d5d867a7ac653fa1d6f29cef4cfb73fad38 |
|
08-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker incorectly enforcing minimal width and height.
The min width and height were enforced with an exception which
is not correct since a view not having enough space should not
terminate the application. Now the insufficient vertical or
horizontal space is propagated by setting the
MEASURED_STATE_TOO_SMALL flag and respecting the constraints
imposed while measuring (consistent with the rest of the View
hierarchy).
bug:5572237
Change-Id: I2dbeb5451d3426cc983b41f6023c7b0fc52c7da3
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| b52d9729bfb2ef7ad50d9a5125ebf3a8322429a9 |
|
07-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker does not hide IME when flinged.
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
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| ec1e06a00d26a783fb948e739ad8157c03e55302 |
|
31-Oct-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updating NumberPicker, TimePicker, DatePicker to fit different screen and font sizes.
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
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| e0c8ab5aaa02d7b9b01fe68fb893af4d78482f6c |
|
26-Oct-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker does not not fit on Crespo in landscape.
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
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 6304b0d58e74509a9f21b67b5227b2fee2f1b60f |
|
20-Oct-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
DatePicker crashes when going from 2036 to 2035 via ▼
1. Some obsolte logic was placing invalid index in the array of
scroll wheel items which was resulting in failure to look its
string representation from the cache causing a NPE.
2. While editing the current value via the IME the middle item
of the scroll wheel was partially visible i.e. the user was
able to see a dimmed version of the old value intermixed with
the new one.
3. The logic for hiding the IME while poking a button i.e. starting
to use another way of changing the current value, was incorrect.
bug:5480205
Change-Id: I1c2c96402bd38bac1dec64ccc6b550410332b9d7
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| b80a3fcad1776c1b9abe3662899660b4f88ac2ab |
|
16-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Revamping of the NumberPicker widget for improved usablility.
1. Now if the widget is not interacted with shows a smaller selector
wheel with the increment and decrement arrows at the top and bottom
respectively.
2. Tapping an arrow button now animates the widget to the new value. i.e.
rotates the selector whell to the next value.
3. Fixed a bug that double tapping on the input shows the IME but then
after pressing an arrow button the IME is not hidden.
4. Fixed a bug that was exposed via late changes in the framework or the
graphics and was manifested of the selector wheel not having fading
edges.
bug:5251980
bug:5383502
Change-Id: I4a089dc69b07a3b28a514017cddf786cb9f4af16
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a53efe9923bedab4fe5d578f32eaff308e5b9e76 |
|
09-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
The time and data pickers did not support IME editor action correctly.
1. Updated TextView to traverse all focusable items. It was searching focus
down and up and was missing right and left focusabled. Updated the focus
seach to use FOCUS_FORWARD and FOCUS_BACKWARD - now all focusable views
are visited.
2. TimePicker and DatePicker were not specifying the IME options for
the next and done editor actions.
bug:5264046
Change-Id: Ief80863fc312582f2f76928bf6e915f620c427e5
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 3fec3fe0e3a83c5e0d1264f34bcc55b158537bc6 |
|
01-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Polish of the accessibility feedback of Date and Time pickers
bug:5228006
bug:5228004
Change-Id: I927e3a6dcbf4f81eab6f506fc38842d8e7a37aa1
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| eeafd4296b7cf4c2ad9c985562f6d70e2a3ffc03 |
|
18-Aug-2011 |
Chet Haase <chet@google.com> |
Fix NumberPicker text positioning.
NumberPicker was making incorrect assumptions about how text was
positioned and centered inside of its controls. This fix changes
the logic of how the scroll wheel draws its text items based on where
the text is positioned inside the EditText that displays the text
by default. This should ensure that the text of the scroll wheel
exactly overlays the text in the EditText view.
Change-Id: I4a7694931f19042bd4142232612490c2ab912d11
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 6a19fcde07527706c2a9175e0b9f2a71549b7ffe |
|
29-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Minor tweak of NumberPicker to draw the scroll wheel at the right locaion
Change-Id: I8429ee1f06f5ef2c41a97c287d598f7c14c22837
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 5203194fdff0c0aaefc405d65871ef0e06e7c682 |
|
29-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Minot twaek of the NumberPicker
Change-Id: I3ab1d27633e7b75f77d09084964cc17edddb9394
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 01fa0d7aae1a551e1e7cfb90d2aeaf2fcb3978af |
|
29-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Date and time pickers do not show properly on phone
1. Copied the default NumberPicker layout to sw-600dip
i.e. in the layouts for tablets and changed the
layout to fit on the screen. No mini calendar on
phones - you need an microsope to see it.
2. Fixed a two pixel off erroro in NumberPicker noticable
when the scroll wheel fades away.
bug:4259424
Change-Id: I07a73faff1e95dffd30424cc8addd35f2fe30e8f
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 092bda57c4b8caad378400b2bc97b9ac66fd2179 |
|
27-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NubmberPicker up/down arrows do not work.
bug:3490963
This is a bug I have introduced while fixing bug:3452868.
Change-Id: Ib2ee39d0c790d60d30bc10051d69f393672a006c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| f66adbe7565ad5dbb75c07dbf36212beeaa582fb |
|
25-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
The NumberPicker input cotrols are somtimes not shown.
bug:3452868
1. Now hiding the input controls, which also cancels the input controls
fade-in animation, on every intercept of down since the fade-in
anumation flips a flag used to guide the drawing of the input controls.
Note that we also want the scroll wheel shown on down but the fade-in
anumation is actually hiding it upon completion.
Change-Id: Ib161ed757e537365b21e6913370d264152dca1fe
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4fd9dae6a23a22142f73749c291c9fd18459e381 |
|
03-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
NumberPicker should not play initial animation while in edit mode
bug:3417930
1. Added a check if the widget is in edit mode to determine if to
play the initial annimation.
Change-Id: Ibcf23fa1ec55a1950323e71eda90da6418b655fb
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 58f51255eb20f9c4d16c11554f372ff92d45fcc7 |
|
27-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
The calendar view widget was jumping incorrectly to the next week
while selectiong the last day of the week.
The NumberPicker widget was getting into an inconsitent state when
reaching the end of the range (non wrapping selector wheel) and
the user touches the location of the hidden increment/decrement
button.
Change-Id: Id54103295dd2574030e2c29996061faa659a5bb7
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 156f20919b3d5f298f8851215adbf65f8b4dc61b |
|
24-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
DatePicker is picking the wrong date
bug:3375074
1. The logic for updating the higher rank fields on wrapping of
lower rank ones was incorrect. Updated that logic.
2. On reaching the min/max date the spinners did not stop
when reaching that date. Now spinners stop at min/max.
3. Fixed a couple of edge case bugs while setting the
the min and max dates of the DatePicker on the fly.
4. Restricted the scrolling/flinging to end at the min
and max dates.
Change-Id: Ibb588ea2cf951cf8d50328bbfbe7ebdad7ee8067
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 1ec1fdfce959069f3092c15d27efc1c2286dc15c |
|
20-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "API REVIEW: android.widget.NumberPicker.OnValueChangedListener" into honeycomb
|
| cedc446684e94c9971c38c3206f1f224314bda2a |
|
20-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
API REVIEW: android.widget.NumberPicker.OnValueChangedListener
Change-Id: I1e739553ab6b99b2768e42cf379a0b155dced81a
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 9cd5fb2f46e219ec8250383fb201b94cb2ee8c0a |
|
20-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Some touches on the NumberPicker UI.
1. Shoing the scroll wheel and fades it out the first time
the widget is displayed.
2. Added separators for easing use to figure out which will
be the current selection while scrolling.
3. Updated the fling scroller to user decelerating interpolator.
Change-Id: Ie75519564ace8f44cc6f8eed692182153f839694
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4243dc394d89a93cb207efa36e9755c2424d688b |
|
19-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updated the Time/Date pickers to be backwards compatible
bug:3349400
Change-Id: I2a3dda82caf7de0ed203306c89ee774b94b7d82e
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 6c742f1e95dfe1f808bf02fadd5fbf9660b95050 |
|
17-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Catching some edge cases while flinging/scrolling in NumberPicker
1. If the scroll is exactly divisible by the scroll item height
the selector wheell is one off from the current value/text input.
Change-Id: I12721e85a99f6a5b51f5ad6f13c3836cb156c9a4
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 012dd5a461f18a2e5dad38c60282fac1c21ff7fe |
|
12-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Renaming NumberPicker resources to be consistent.
1. The resources for the NumberPicker now start with 'numberpicker_' instead of the legacy 'timepicker_'
2. Removed unused resources.
Change-Id: Ide7c61df1936f174b6fffc778cba3a58b324556a
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 34c0688ceafbeef2648bd2287b3b3c3801679448 |
|
03-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Fixed the NumberPicker to adjust to the closest value while scrolling/flinging
Change-Id: I782603d9a187d0ce9196e3fc90f28e372637584c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 51c52edad7d40697d7fb2a091f850506fa897643 |
|
28-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
3313982 DatePicker/TimePicker allow users to scroll date/time even when disabled.
Change-Id: I8c28615bfc813dfdddf21c40d84cc7c36f1fd391
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| e9730bf3d2dcbea1879f24c18aaf9810ac57084c |
|
21-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding APIs for setting whether to show week number and setting the start day of week. Cleaned up the code a bit.
Change-Id: Iaa7154c6912a68cd91df3ac881c324096394ea24
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 28104e1de5595a22a6987181b13ddeb192739afd |
|
20-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
3298147 DatePicker dialog does not provide mechanism for specifying range from which to select
Change-Id: Ib5dd7db90ccc5b4d984914c481118049ac3648fe
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| bf80562d22b2bbe7944d80d0524c69d0238010cb |
|
18-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Bug 3191746. atePicker TimePicker: Dark theme is used in a Light theme app
Change-Id: I20d0cca3b78af9db80854a57c88d6cab3b00f555
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 2b9484f453ef307880a93240bb050b39af72bee2 |
|
18-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Bug 3293819. Timepicker is showing single digit for 0, 1, 2 minutes (the rest are fine)
Change-Id: I55c50857740fc1210c45e9b7fc8905ec2266ed8c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| c75ec3324e9e3e6500148cc2978caab90ea962e4 |
|
17-Dec-2010 |
Chet Haase <chet@google.com> |
Fix for TimePicker not redrawing itself.
The problem was that NumberPicker override View.draw(), but did not
call the superclass version of the method in some situations. This
resulted in the DIRTY flag for the view not getting cleared properly,
and future invalidations not propagating correctly.
The fix was to call super.draw() from NumberPicker.draw().
Change-Id: Ic17215dea86d54b77375494ada124dd6970e3ad6
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 99b539f6326a5f0df123b34766becec023bf7a84 |
|
15-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updating the light Date picker theme. Some UI fixes.
Change-Id: Ic83fdf93868bf86478a1173e82f24ac27f6301bc
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| a911d4a2b1be7e9ea909a579167826e4a5bac1a3 |
|
09-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
bug_3259956 and bug_2166704
Change-Id: I71b4cc3c1111e7a4e78fb276d54a291c22fb2752
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 4bfd794475e6fb34c9dfa83d4302e9db365a3709 |
|
08-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Updated the NumberPicker for exposing it into the SDK
Change-Id: I3bd48d0210da8a202b6ff60deecb5d7776f1b73b
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 3119fd426d0e975541b1b8207ff13e2cce443c73 |
|
08-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Fixing the build breakage
Change-Id: I8589e5fcdeec127c84d2b419f6ef44d7011a5a6b
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 50f34d14f6dd3411fdbdb6a7b8b285c2b8fdbf5c |
|
04-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding DatePciker widget based on the Calednar team code. Updated DatePciker and DatePickerDialog as the second part of the Time/Date pciker refresh feature.
Change-Id: Id32c614bcd799463ca33bf08fb7d5cf44f8326a6
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| f0ef665299d795df7905897e1c337e37891dafef |
|
06-Dec-2010 |
Jean-Baptiste Queru <jbq@google.com> |
Merge from gingerbread-plus-aosp
Change-Id: I154071687cdd51c28bb377ea3f1e818e96909b56
|
| 005dd44b756ccd5812ac55f07f93e3e16ce2be0b |
|
06-Dec-2010 |
Jean-Baptiste Queru <jbq@google.com> |
am 864b1e00: Merge "NumberPicker: Set formatter local value to US."
* commit '864b1e007dc741ec10c23cabc0271f97a5b8c598':
NumberPicker: Set formatter local value to US.
|
| f04f7ae73b0a97eb90797ead07553303d0b383f9 |
|
06-Dec-2010 |
Chen Libao <libao.chen@sonyericsson.com> |
NumberPicker: Set formatter local value to US.
As the Arabic language formatter would make number "1,2,3" to Arabic
language word means one,two,three, NumberPicker won't like to show
any thing other than numbers, add local settings to US, make the
number 1,2,3
Change-Id: If2d161ac4133f6c9c6e1ec284d6d2fbf01855fa0
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 206316a61f904ea0a6b106137dd7715a2c246d4c |
|
19-Nov-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
New Number picker widget
Change-Id: I834e725b58682e7a48cc3f3302c93c57b35d4e27
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 8bcbebd4178b2e9aca9ee3bd9e1e12c42e74c8db |
|
02-Oct-2010 |
Adam Powell <adamp@google.com> |
Fix bug 3024080 - Date picker month field uses numeric text field
NumberPicker now uses text entry when displayed value strings are
provided.
Change-Id: I555a7d6b64ad6a5af131b3e1d8c638dcdb00d02c
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| aa516beb79693ceffbd81a7c9d14c940e412cccb |
|
06-Mar-2010 |
Romain Guy <romainguy@android.com> |
Correctly validate numbers when pasted in NumberPicker.
Bug #2258525
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 7722abe2591026e7db8910afa0431602723fc1e0 |
|
04-Feb-2010 |
Paul Westbrook <pwestbro@google.com> |
Bug 2420366
Rehide NumberPicker widget
/frameworks/base/core/java/android/widget/NumberPicker.java
|
| 68f2f547f56f239b60d13b2b62a08a65874f6662 |
|
13-Jan-2010 |
Paul Westbrook <pwestbro@google.com> |
Bug 2330111
Make NumberPicker public
Made setCurrent() more robust, as the value needs to be within the range
specified earlier. setCurrent() will now throw an exception
if the specified doesn't fall in the range
/frameworks/base/core/java/android/widget/NumberPicker.java
|