I have been testing ubiquity-kde today/tonight with 10.04.4 LTS, 11.10,
and 12.04. Having done so, I have always tabbed to continue and pressed
enter w/o any issues. Alt+C also worked w/o issues. Is this still an
issue for anyone else? If so, feel free to reopen this report with any
further
Original complaint was addressed here:
---
ubiquity (1.99.22) karmic; urgency=low
[ Michael Terry ]
* kde: Let back/forward/quit buttons activate when highlighted and the
user presses Enter. Part of bug #46600
--
cannot select `continue' with keyboard in kde
I pushed a fix for the original complaint: that pressing Enter doesn't
activate those buttons, by marking Back/Forward/Quit as 'AutoDefault'.
They were always activatable by pressing Space.
Colin, to address your issue, seems that the main window has to be a
QDialog. The Qt documentation
This is still a valid and important issue. You had no justification for
closing it.
** Changed in: ubiquity (Ubuntu)
Status: Invalid = Triaged
--
cannot select `continue' with keyboard in kde
https://bugs.launchpad.net/bugs/46600
You received this bug notification because you are a
Was this still an issue in the final version of Dapper(?) ?
** Changed in: ubiquity (Ubuntu)
Status: Confirmed = Invalid
--
cannot select `continue' with keyboard in kde
https://bugs.launchpad.net/bugs/46600
You received this bug notification because you are a member of Ubuntu
Bugs,
I tried to fix this by (a) setting the default property on the next
button in the .ui file and, separately, (b) putting
self.userinterface.next.setDefault(True) after everything that
programmatically enables the next button. Neither worked: the next
button was the default for the first step, but
