Opened 11 years ago
Closed 10 years ago
#4309 closed defect (fixed)
"Timezone" does not auto-scroll
Reported by: | ajay_garg | Owned by: | erikos |
---|---|---|---|
Priority: | Low | Milestone: | Unspecified |
Component: | Sugar | Version: | Git as of bugdate |
Severity: | Unspecified | Keywords: | Australia, 13.1.0, regression |
Cc: | JerryV | Distribution/OS: | Fedora |
Bug Status: | Unconfirmed |
Description
In the development build 16 on XO-1.75, I notice the following ::
a)
Open "My Settings" -> "Date and Time".
b)
Search for a timezone (Australia/Sydney) interactively, using the entry-box.
The auto-scroll WORKS FINE here, as the auto-scroll is done to "Australia/Sydney"
c)
Click "tick" to save the selected timezone, and exit the section.
d)
Re-enter the section.
e)
It is observed that the auto-scroll HAS NOT TAKEN PLACE to "Australia/Sydney". However, if I manually scroll, I see that "Australia/Sydney" is selected == it's just that the auto-scroll did not take place.
At code level ("/usr/share/sugar/extensions/cpsection/datetime/view.py"),
def setup(self):
zone = self._model.get_timezone()
for row in self._store:
if zone == row[0]:
self._treeview.set_cursor(row.path,
self._timezone_column,
False)
self._treeview.scroll_to_cell(row.path,
self._timezone_column,
True, 0.5, 0.5)
break
here, "self._treeview.set_cursor" is working at all times, but "self._treeview.scroll_to_cell" does not work in steps d) and e).
This is a regression; auto-scroll worked fine in steps d) and e) in 12.1.0.
Change History (7)
comment:1 Changed 11 years ago by ajay_garg
comment:2 Changed 11 years ago by ajay_garg
- Keywords 13.1.0 added
comment:3 Changed 11 years ago by dsd
- Priority changed from Unspecified by Maintainer to Low
comment:4 Changed 10 years ago by JerryV
- Cc JerryV added
- Keywords Australia added
comment:5 Changed 10 years ago by JerryV
- Keywords changed from Australia 13.1.0, regression to Australia, 13.1.0, regression
comment:6 Changed 10 years ago by dnarvaez
- Milestone changed from 0.98 to Unspecified
comment:7 Changed 10 years ago by dnarvaez
- Resolution set to fixed
- Status changed from new to closed
Seems to work here, hopefully fixed.
Note that, there is no traceback/warning in shell.log.