Auto-show Onboard when clicking an already focused text entry

Bug #1078602 reported by marmuta on 2012-11-14
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Onboard
Undecided
marmuta
ubuntu-nexus7
Medium
marmuta

Bug Description

Taken from
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1071508/comments/2#

Case 1
If you are editing a simple text document and you closed the keyboard accidently, you can not just retouch in the inpit-field to re open the keyboard. You have to touch somewere else and than back in input-field to reopen it.

Case 2
"Save as" dialog. If you editing the name of the file that you wont to save and you closed the keyboard again accidently, you can not just re-touch in the inpit-field to re open the keyboard.

marmuta (marmuta) wrote :

I've looked into this and believe we can do it, as long as the click changes caret position.

First question is, do we want Onboard to show on every click? The hide button is there to get Onboard out of the way, for whatever reason. I believe just looking through a document should be possible without obstruction on every click, accidental or not. So I tend to think we should try it for Case 2 only, i.e. for single line text entries (anything but ATSPI_STATE_MULTI_LINE).

Mirzet, the other question is, is it too easy to hide Onboard accidentally? Which button are you trying to press when that happens? Note that the move button of v0.98x isn't working properly on touch screens. This is fixed trunk.

summary: - Auto-show Onboard when clicking and already focused text entry
+ Auto-show Onboard when clicking an already focused text entry
Mirzet Kadic (caracal-enl) wrote :

I agree with this proposal, as far as I have understood everything correctly. progress is always good. :-)

There is not a tipical case where you always hitting the hide button accidently but if you do, you will be very confused especially in conbination with this bugs:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077277
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1076607
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1077260
https://bugs.launchpad.net/ubuntu-nexus7/+bug/960537

I allready noted that with the move button.

marmuta (marmuta) wrote :

Done in trunk. Seems to be quite useful, thanks for the suggestion, Mirzet.

Note, as I wrote above, in order for the keyboard to show up, the caret position of the clicked text entry has to change. I did experiment with a more general approach to detect any click, but this didn't work out.

Changed in onboard:
status: New → Fix Committed
Robert Bruce Park (robru) wrote :

Hey Marmuta, this fix was committed a month ago, when will it be released? ;-)

Changed in ubuntu-nexus7:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → marmuta (marmuta)
Changed in onboard:
assignee: nobody → marmuta (marmuta)
marmuta (marmuta) wrote :

Thanks for the reminder. It is released, with 0.99 alpha at least, I guess that counts. There are a bunch of other bugs to close too. I was too focused on tackling bug #905636, recently.

Changed in onboard:
status: Fix Committed → Fix Released
Changed in ubuntu-nexus7:
status: Fix Committed → Fix Released
joe (jeremyledoux1) wrote :

First time using this system so apologies if I am doing this wrong. I noticed a issue I had with the keyboard was it wouldn't show when a screensaver came on. If you don't have a physical keyboard you are locked out unless you reinstall. I think a workaround is not to include a screensaver function as it will eliminate this issue and wont have to worry about it sucking power instead of going to standby mode.

Francesco Fumanti (frafu) wrote :

As a reply to message #6:

Thanks for your interest in Onboard and for telling us your problem.

Could you please verify whether the "Show when unlocking the screen" checkbox in the Onboard Preferences is enabled? If it is and anboard does not appear, please file a new bug (there is a link at the topright of this page to report bugs), as it is a different problem as the one from this thread.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers