IssueTracker

Setting the minimum or maximum date does nothing if the previous min/max has the same year as the new min/max. The methods also misbehave if the year is different while the day of the year is the same.

I think the bug is clear in the source code. A short-circuit occurs in the first if-statement when the new min date has the same year as the old min date, even if the days are different. Furthermore, I the second portion of that statement should use the == comparison, rather than !=, since the function simply returns if the years don't match but the days do.

    /**
     * Sets the minimal date supported by this {@link NumberPicker} in
     * milliseconds since January 1, 1970 00:00:00 in
     * {@link TimeZone#getDefault()} time zone.
     *
     * @param minDate The minimal supported date.
     */
    public void setMinDate(long minDate) {
        mTempDate.setTimeInMillis(minDate);
        if (mTempDate.get(Calendar.YEAR) == mMinDate.get(Calendar.YEAR)
                                                              ^^---bug here
                && mTempDate.get(Calendar.DAY_OF_YEAR) != mMinDate.get(Calendar.DAY_OF_YEAR)) {
                                                                                     ^^---and here
            return;
        }
        mMinDate.setTimeInMillis(minDate);
        mCalendarView.setMinDate(minDate);
        if (mCurrentDate.before(mMinDate)) {
            mCurrentDate.setTimeInMillis(mMinDate.getTimeInMillis());
            updateCalendarView();
        }
        updateSpinners();