** No longer affects: ubuntu-ui-toolkit
--
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1346669
Title:
Time Picker behaves erractically when min and max is set
Status in “ubuntu-ui-toolkit” package in Ubuntu:
Confirmed
Bug description:
Using this example qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
import Ubuntu.Components.Pickers 1.0
MainView {
width: units.gu(48)
height: units.gu(60)
Column {
DatePicker {
id: datePicker
objectName: 'datePicker'
mode: 'Years|Months|Days'
maximum: {
var d = new Date()
d.setFullYear('2030')
return d
}
minimum: {
var d = new Date()
d.setFullYear('1990')
return d
}
date: {
var d = new Date()
d.setFullYear('2010')
d.setMonth('5')
d.setDate('15')
return d
}
}
DatePicker {
id: timePicker
objectName: 'timePicker'
mode: 'Hours|Minutes|Seconds'
maximum: {
var d = new Date()
d.setFullYear('2030')
return d
}
minimum: {
var d = new Date()
d.setFullYear('1990')
return d
}
date: {
var d = new Date()
d.setHours(12)
d.setMinutes('30')
d.setSeconds('30')
return d
}
}
}
}
The timepicker behaves erractically. When selecting a minute, the
hour picker. When selecting things with the second picker, both the
hour and minute pickers advance forward as well.
It's interesting the min and max dates are being set (this was
discovered trying to workaround bug https://bugs.launchpad.net/ubuntu-
calendar-app/+bug/1328600) as a timepicker likely doesn't make sense
to have a year, but since they can be set the pickers likely should
behave properly when done so.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1346669/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help : https://help.launchpad.net/ListHelp
