| c255800fb0f46ea5f68d2c145605ac7dcd3a89b6 |
|
01-May-2013 |
Elliott Hughes <enh@google.com> |
am 6d82f86f: Merge "Show CJK dates as all-numeric in the DatePicker."
* commit '6d82f86fa01800ee0523743366e0dc1113178fd9':
Show CJK dates as all-numeric in the DatePicker.
|
| 949e9df25bccb736675f950591d3a286ae4052fc |
|
30-Apr-2013 |
Elliott Hughes <enh@google.com> |
Show CJK dates as all-numeric in the DatePicker.
Before, we'd have something like 2006 4月12. After, we have 2006 4 12.
The alternative would require using custom NumberPicker.Formatter instances
for the year and day fields in these locales, and that seems significantly
more disruptive.
Bug: 8766552
Change-Id: I568578aae2f80f2acfc53cd277ef3beae6743472
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 76c643c9b600ef31c22f807c2874c879a7fa5069 |
|
30-Apr-2013 |
Elliott Hughes <enh@google.com> |
am e3f2735f: Merge "when locale is non-Enligh, sometimes month spinner needs a number IME"
* commit 'e3f2735fcfd8dafd226200d5cf219a6f82c9cc0c':
when locale is non-Enligh, sometimes month spinner needs a number IME
|
| e3f2735fcfd8dafd226200d5cf219a6f82c9cc0c |
|
30-Apr-2013 |
Elliott Hughes <enh@google.com> |
Merge "when locale is non-Enligh, sometimes month spinner needs a number IME"
|
| a99595a393341b6a130e202bc9e93848ee53057b |
|
30-Apr-2013 |
Elliott Hughes <enh@google.com> |
am afe56810: Merge "Fix DatePicker\'s spinner order in various locales."
* commit 'afe56810517a4ddfad125029ca04fd4cc5af2ef5':
Fix DatePicker's spinner order in various locales.
|
| 659f145278ffd85f934a435dbec47ead685caf59 |
|
30-Apr-2013 |
Elliott Hughes <enh@google.com> |
Fix DatePicker's spinner order in various locales.
DatePicker always effectively uses yyyy MMM dd, so we need to ask
icu4c what order those should appear in for the user's locale. The
existing DateFormat code was an approximation that worked for en_US
but not for all languages (fa being one example).
Bug: 7207103
Change-Id: I7b12568dbc02522ebad6e1db5f8426109cd6f7ce
/frameworks/base/core/java/android/widget/DatePicker.java
|
| e9a74a1a31f82391d44840aa17293021fcab6837 |
|
20-Mar-2013 |
Hyejin Kim <hyejin.kim@lge.com> |
when locale is non-Enligh, sometimes month spinner needs a number IME
When locale is non-English like korean, chinese, etc.,
month displayed string is started with number.
So, It's better to use Number IME for month selection.
Change-Id: If0444d62679b1f31d98fdedd2f06c2d445cade2a
/frameworks/base/core/java/android/widget/DatePicker.java
|
| e10837f444c3da40a50a269e696afac63729bce3 |
|
08-Mar-2013 |
Svetoslav <svetoslavganov@google.com> |
[DO NOT MERGE] DatePickerDialog title initially incorrect if calendar view shown.
If the calendar view of the date picker dialog is shown we
do not use a formatted date as the dialog title since the
calendar view shows it, instead we show a static "Set date"
title. However, the initial state of the date picker dialog
on a tablet has a formatted date since the date picker widget
does not do a correct check whether the calendar view is shown
which returns a false negative resulting in a title with a
formatted date being added since the dialog thinks it has no
calendar view.
Change-Id: Ibf4c433b34ab1ee1bc1dc386689664a32283fb6a
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| 4c359b76f9a030f92a302ba74a528faa170bad4e |
|
25-Jul-2012 |
Scott Main <smain@google.com> |
docs: fix a bunch of links from javadocs to api guides
and add some attributes to Spinner and Switch
Change-Id: If015ad000c1a36e19904c132e98ebff1ceaf718b
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.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/DatePicker.java
|
| c49a8be0d2aee5a3d1ff50015a0c0758b0988cfb |
|
02-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Sync of the DatePicker attributes with the public Java APIs.
1. Deprecated two old attributes.
2. Renamed an attribute which is not mean to be public so
its name is not the same as that of an already public one.
bug:6094713
Change-Id: I577a9e191cbd05cd18cb34105dcdbe53c0a5dd1e
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.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/DatePicker.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/DatePicker.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/DatePicker.java
|
| f5926962cc665d4a2e6464f9ba9e3e9788496a6f |
|
12-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Date/time pickers and calendar view not handling locale change.
1. The data/time pickers and calendar view do not handle locale
change properly since they use cached Calendar instances to
limit the GC but fail to update them when the local changes.
Change-Id: I2a92d7f4e0f2798422843123e5aa483f8044bbed
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 736c2756bf3c14ae9fef7255c119057f7a2be1ed |
|
23-Apr-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration feature, event bubling, refactor
1. Added an Input Filter that interprets the touch screen motion
events to perfrom accessibility exploration. One finger explores.
Tapping within a given time and distance slop on the last exlopred
location does click and long press, respectively. Two fingers close
and in the same diretion drag. Multiple finglers or two fingers in
different directions or two fingers too far away are delegated to
the view hierarchy. Non moving fingers "accidentally grabbed the
device for the scrren" are ignored.
2. Added accessibility events for hover enter, hover exit, touch
exoloration gesture start, and end. Accessibility hover events
are fired by the hover pipeline. An accessibility event is
dispatched up the view tree and the topmost view fires it.
Thus predecessors can augment the fired event. An accessibility
event has several records and a predecessor can optionally
modify, delete, and add such to the event.
3. Added onPopulateAccessibilityEvent and refactored the existing
accessibility code to use it.
4. Added API for querying the currently enabled accessibility services
by feedback type.
Change-Id: Iea2258c07ffae9491071825d966dc453b07e5134
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 3fb3d7c4e756bd32d5abde0abca9ab52d559bc84 |
|
23-Apr-2011 |
Adam Powell <adamp@google.com> |
Revert "Touch exploration feature, event bubling, refactor"
This reverts commit ac84d3ba81f08036308b17e1ab919e43987a3df5.
There seems to be a problem with this API change. Reverting for now to
fix the build.
Change-Id: Ifa7426b080651b59afbcec2d3ede09a3ec49644c
/frameworks/base/core/java/android/widget/DatePicker.java
|
| ac84d3ba81f08036308b17e1ab919e43987a3df5 |
|
05-Apr-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration feature, event bubling, refactor
1. Added an Input Filter that interprets the touch screen motion
events to perfrom accessibility exploration. One finger explores.
Tapping within a given time and distance slop on the last exlopred
location does click and long press, respectively. Two fingers close
and in the same diretion drag. Multiple finglers or two fingers in
different directions or two fingers too far away are delegated to
the view hierarchy. Non moving fingers "accidentally grabbed the
device for the scrren" are ignored.
2. Added accessibility events for hover enter, hover exit, touch
exoloration gesture start, and end. Accessibility hover events
are fired by the hover pipeline. An accessibility event is
dispatched up the view tree and the topmost view fires it.
Thus predecessors can augment the fired event. An accessibility
event has several records and a predecessor can optionally
modify, delete, and add such to the event.
3. Added onPopulateAccessibilityEvent and refactored the existing
accessibility code to use it.
4. Added API for querying the currently enabled accessibility services
by feedback type.
Change-Id: Iec03c6c3fe298de3f14cb6efdbb9b198cd531a0c
/frameworks/base/core/java/android/widget/DatePicker.java
|
| f583dd37643f495642cd64e9b8e6a0a9e0836ff1 |
|
18-Mar-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
DatePicker does not respect the user preference of date format
bug:4124142
The DatePicker was not properly interpreting the current date
format and was ingoring user preferences for the date format
rather it was using the locale default all the time.
Change-Id: I195c2ad975dc4e9adc5b6eb70c33c909a1553113
/frameworks/base/core/java/android/widget/DatePicker.java
|
| bc006dc0aa1c149508a3196a40bac62cf1b33b84 |
|
25-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
am dc365a36: Merge "resolved conflicts for merge of 66edf2bb to honeycomb-plus-aosp" into honeycomb-plus-aosp
* commit 'dc365a36dac50bccc1411c37839513daec56d335':
Use different version of CLDR data in DatePicker
|
| f114809031c5e5017bf69ab7a6d01024f1745fc8 |
|
25-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
resolved conflicts for merge of 66edf2bb to honeycomb-plus-aosp
Change-Id: I687ca9b7873890e3b30da16d5dde6b57ce92f0d6
|
| ef7ec7a029425bfb42be1476261c463c424f70be |
|
25-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Use different version of CLDR data in DatePicker
The ICU CLDR data doesn't use the month abbreviations that are
appropriate for the DatePicker, so use the framework copy of the CLDR
data.
Bug: 2641810
Note: cherry-picked from Honeycomb
Change-Id: I3c045dbfb751b8b7ce6361b5a67407206fc64db1
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 5f3f6ce154ca1a0075f8ca13872d74f935acbe3d |
|
25-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Exposing the CalendarView of the DatePicker.
bug:3272194
1. Added a getter to DatePicker.
Change-Id: If0c7fee4ab5f6abf6b12a02dbd5d519c00683115
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 13427a04de835677f9e5f727298f168b88faa562 |
|
01-Feb-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Clean up of the DatePicker
1. Removed a duplicate DatePicker stylable.
2. Fixed a bug that if the user wrongly desires to have the
calendar view and spinners hidden despite that DataPicker
ovrrides such incorrect choice to show at least the spinners
the min adn max date attributes are igonored.
Change-Id: I6307db71aca837ad790aea59fa70ead393feb066
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 8a2a89588c3889b999a8fffa2d7c7a5c3ce25eb8 |
|
28-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility support to NumberPicker, DatePicker, and TimePicker
bug:3400707
Change-Id: I0d4b10e9c744e7221a9a7a74081bcee351abbaf2
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.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/DatePicker.java
|
| cedc446684e94c9971c38c3206f1f224314bda2a |
|
20-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
API REVIEW: android.widget.NumberPicker.OnValueChangedListener
Change-Id: I1e739553ab6b99b2768e42cf379a0b155dced81a
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| 9a143e6641fa4a5942e7341007d916601402e8df |
|
18-Jan-2011 |
Dirk Dougherty <ddougherty@google.com> |
Doc change: fix busted link to DatePicker tutorial.
Change-Id: I957aa3bb4c0c91f195de99405cc8e1b5a5bc82f7
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 3d20c846e45141acfbe9a56f0518ddb7a0bb4cf9 |
|
17-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Ensure that no callback is invoked while initializing DatePicker
bug:3360821
1. While my previous change:I3baff68c has partially fixed this bug
it was still possible for a callback to be invoked on init. If a
callback was already regitsered and the init is called the
callback is incorrectly notified.
Change-Id: I05c6cb78f4c7b7d2a00c52aef42c1698d9479be5
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 2f136a874d240cc7e85e8de9c7644a7daa9532da |
|
13-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
DatePicker is calling back its listener on init.
bug:3341515
1.Changed the callbeack registration to follow the spinners
initialization.
Change-Id: I3baff68c295993f975beec2b376af88e32b24e20
/frameworks/base/core/java/android/widget/DatePicker.java
|
| d7419986ca79e5408f247fbfcad2c5dc2966a9e0 |
|
12-Jan-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Down arrow on the month can end up at the start of the month
bug:3338078
1. The bug was that I was claculating delta month and day from
the current date but was changing the latter in the middle
thus causing inconsistent state.
Change-Id: Id3082b01778fc2b3116aa412aff3f12e9ebf0c97
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 25f84f323c607bbd9133432fd789ba29b2dcd4d4 |
|
30-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
3316147 TimePicker and DatePicker is editable even after the first setEnabled(false).
Change-Id: If800b048973200d249b1f5c62af064392ed98d91
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.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/DatePicker.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/DatePicker.java
|
| a911d4a2b1be7e9ea909a579167826e4a5bac1a3 |
|
09-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
bug_3259956 and bug_2166704
Change-Id: I71b4cc3c1111e7a4e78fb276d54a291c22fb2752
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| 3119fd426d0e975541b1b8207ff13e2cce443c73 |
|
08-Dec-2010 |
Svetoslav Ganov <svetoslavganov@google.com> |
Fixing the build breakage
Change-Id: I8589e5fcdeec127c84d2b419f6ef44d7011a5a6b
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| dddda8d188408ff18935b1b0e15a00fe012a03da |
|
15-Nov-2010 |
Kenny Root <kroot@google.com> |
Use different version of CLDR data in DatePicker
The ICU CLDR data doesn't use the month abbreviations that are
appropriate for the DatePicker, so use the framework copy of the CLDR
data.
Bug: 2641810
Change-Id: Ic0f7b461b43c76dfa3f8b73a9479b79df230d7bd
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| 70c9ffbc838271f0ea27a4780eb146287de53ef6 |
|
20-Aug-2010 |
Scott Main <smain@google.com> |
am 11a72482: Merge "docs: add links from widget classes to tutorials" into froyo
Merge commit '11a72482a0cdc45ceaf4ca83957e682381455aee' into gingerbread
* commit '11a72482a0cdc45ceaf4ca83957e682381455aee':
docs: add links from widget classes to tutorials
|
| 41ec65355bd6ded652769725b276d47c54a0d913 |
|
20-Aug-2010 |
Scott Main <smain@google.com> |
docs: add links from widget classes to tutorials
Change-Id: I817e885524951853182b0458df4a32dea1614243
/frameworks/base/core/java/android/widget/DatePicker.java
|
| f78964490d8098387d51444c87bf520ad3f674e2 |
|
06-May-2010 |
The Android Open Source Project <initial-contribution@android.com> |
merge from open-source master
Change-Id: Ia9e1f4e049f5870386ea29ddb6e3ef028ea918da
|
| 0ba2d4782c62df6538399f80a91abe3867c449df |
|
03-May-2010 |
Nicholas Killewald <captainspam@gmail.com> |
Fixed deserialization problem in DatePicker.
During onRestoreInstanceState for DatePicker, the internal
state of the widget is restored properly (thus setting the
internal year, month, and day), but the spinners aren't
visually updated to that state immediately. That is to say,
the internal state of the widget doesn't match the spinners
in that case, which can cause confusion.
Change-Id: I96d1a299d0ee159d41450470acb30a3bf6006d44
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 9161e202d18ff31946fcd320641bc53abdc61afe |
|
09-Mar-2010 |
The Android Open Source Project <initial-contribution@android.com> |
merge from open-source master
Change-Id: I66d3db4c9ed3f54ce17a8d64ca0c6cce6941cdaa
|
| e3491b6b5f1d3fb871074766597b275d9f682faa |
|
05-Mar-2010 |
Kenneth Andersson <kenneth.andersson@sonyericsson.com> |
Title in DatePickerDialog used in Settings application not updated correctly
The DatePickerDialog in the Settings application is not updated correctly if you follow
the following step-by-step:
1. Enter Date option in settings application
2. Modify the values of the date, then cancel the changes
3. Once again enter the date option
and you can see that the title in the dialog has not been updated correctly. This is
due to a missing call to onDateChanged callback in the DatePicker class. Solution was
to add the notify call when updateTime has been called.
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 5fe1e6221ea3bab3120f5b9c0ceacaf59d116c05 |
|
10-Feb-2010 |
Eric Fischer <enf@google.com> |
Make the Date Picker fields more consistent in locales with numeric months.
In locales that use month numbers instead of names, use *just* the number
instead of also the word for month to be consistent with the other fields,
which also show just a number instead of a number plus the word for day
or year.
Bug 2289276
/frameworks/base/core/java/android/widget/DatePicker.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/DatePicker.java
|
| 7762d93621f508f4410fd37b5bbdfec0071b0420 |
|
11-Dec-2009 |
Paul Westbrook <pwestbro@google.com> |
Unbundling work
Moved AndroidHttpClient, Rfc822InputFilter, Rfc822Validator
NumberPicker, NumberPickerButton to android-common
---
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 03a8017d0fe3b55b69c4328aa0d27bd96a2f1360 |
|
24-Jul-2009 |
Eric Fischer <enf@google.com> |
Make the DatePicker respect the date format setting if the date is numeric.
In some locales, there are no abbreviated month names; the abbreviated
date formats are essentially numeric. If the user is in such a locale,
have the DatePicker respect the date format setting so that the order
of the fields will match other numeric-only dates.
In locales that have abbreviated month names, continue to use the order
that is normal in spelled-out dates.
And update the order in updateDate() so that the new order is reflected
if you change the order setting and immediately go to change the date
without leaving and returning to the Date & Time settings in between.
At the same time, change DateFormat.getDateFormatOrder() back to working
the way it did in cupcake (prioritizing the date order preference over
the locale), even though the DatePicker no longer calls the method.
Bug 1805085
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 2bf761c20253222a763bce9a63d14c48ab08a556 |
|
14-Jul-2009 |
Suchi Amalapurapu <asuchitra@google.com> |
Fix couple of issues in DatePicker
The NumberPicker's listener needs to be invoked only if
the current value changes when validating input.
This removes the some unwanted duplicate calls to onChanged.
Adjust day for month and leap years. note that updateDaySpinner
directly sets the value on day picker and doesn't invoke the
listener twice
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/widget/DatePicker.java
|
| d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/widget/DatePicker.java
|
| da996f390e17e16f2dfa60e972e7ebc4f868f37e |
|
13-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@131421
/frameworks/base/core/java/android/widget/DatePicker.java
|
| f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/frameworks/base/core/java/android/widget/DatePicker.java
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/widget/DatePicker.java
|