Obsolete
Status Update
Comments
ss...@google.com <ss...@google.com> #3
Hi,
please attach your sample android project which reproduces the issue, zip it and share(just to avoid the confusion between your sample code and the one we create to replicate the issue,sample code is requested here).
explain expected and observed behavior? Attach screen shots for more clarity.
Which device and build the issue observed on?
Explain the steps to reproduce the issue with your apk. Provide all necessary information to reproduce the issue.
Note: Please upload the attachments to google drive and share the folder to android-bugreport@google.com, then share the link here.
please attach your sample android project which reproduces the issue, zip it and share(just to avoid the confusion between your sample code and the one we create to replicate the issue,sample code is requested here).
explain expected and observed behavior? Attach screen shots for more clarity.
Which device and build the issue observed on?
Explain the steps to reproduce the issue with your apk. Provide all necessary information to reproduce the issue.
Note: Please upload the attachments to google drive and share the folder to android-bugreport@google.com, then share the link here.
mi...@gmail.com <mi...@gmail.com> #4
I have finished a demo app that reproduces such as shown in above screenshots. The zip in this folder contains the project, other things include screenshots of application, and a ReadMe file, it contains all the information about expected behavior and actual outcome, device information and steps to reproduce same problem.
https://drive.google.com/folderview?id=0BzimhbpXN0FaeWpqTzBMZUk1eGc&usp=sharing
ss...@google.com <ss...@google.com> #5
Hi,
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
is...@google.com <is...@google.com>
sa...@google.com <sa...@google.com> #6
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
This issue is happening only in newer DatePickerDialogs introduced after 5.0. In 5.X devices, datepickers are vertically scrolling, so this problem doesn't bother much, but in marshmallow, this is really a problem for devices with small screens.
I am using Micromax Canvas A1 with Android 6.0.1
If I don't use mFromDate object to set time of Calendar, everything goes fine. Here is the code:
if(mFromDate == null){
displayErrorMessage(mFromDateTextView, "Please select from date first");
return;
}
final Calendar calendar = Calendar.getInstance();
if(mToDate != null){
calendar.setTime(mToDate);
}
mToDateDialog = new DatePickerDialog(this, new DatePickerDialog.OnDateSetListener() {
@Override
public void onDateSet(DatePicker view, int year, int monthOfYear, int dayOfMonth) {
Calendar calendar1 = new GregorianCalendar(year, monthOfYear, dayOfMonth);
mToDate = calendar1.getTime();
SimpleDateFormat simpleDateFormat = new SimpleDateFormat("dd-MMM-yyyy");
mToDateString = simpleDateFormat.format(mToDate);
mToDateTextView.setText(mToDateString);
}
}, calendar.get(Calendar.YEAR), calendar.get(Calendar.MONTH), calendar.get(Calendar.DAY_OF_MONTH));
if(mFromDate != null){
calendar.setTime(mFromDate);
mToDateDialog.getDatePicker().setMinDate(mFromDate.getTime());
Date currentDate = new Date();
calendar.add(Calendar.DAY_OF_MONTH, 90);
if(currentDate.compareTo(calendar.getTime()) < 0){
mToDateDialog.getDatePicker().setMaxDate(currentDate.getTime());
}else{
mToDateDialog.getDatePicker().setMaxDate(calendar.getTimeInMillis());
}
}
mToDateDialog.setCanceledOnTouchOutside(false);
mToDateDialog.requestWindowFeature(Window.FEATURE_NO_TITLE);
mToDateDialog.show();