|
Back in the days of the April release for SHR-Testing, the keyboard wouldn't auto-display, and I thought that was somewhat inconvenient, so I was happy when I upgraded to SHR-U and saw that the keyboard would auto-display when I clicked in text fields.
However, I've found that the behavior is more annoying than having to pull up the keyboard when I want it. There are many times that a program will automatically put the cursor into a text field, and I don't want to do anything with that text field, so I have to manually close the keyboard. Then I click somewhere else on the screen, and it happens to go into a text area again... the keyboard auto-displays, and I have to manually close it again. Is there a configuration that I can tell it to only display and hide manually? I want it to stay invisible until I want it, and I want it to stay visible until I'm done... indicated by hitting the button to activate / deactivate. I don't want it to try to interpret when it thinks I want it and when I don't. I've searched the mailing list using Nabble, and the only thing I found was from when the matchbox keyboard was a separate application, and there was a separate configuration (/etc/matchbox/session). Unfortunately that path doesn't exist in the December release. Thanks for any info. -Laura |
|
On Tue, Jan 5, 2010 at 18:33, vancel35 <[hidden email]> wrote:
> > Back in the days of the April release for SHR-Testing, the keyboard wouldn't > auto-display, and I thought that was somewhat inconvenient, so I was happy > when I upgraded to SHR-U and saw that the keyboard would auto-display when I > clicked in text fields. > > However, I've found that the behavior is more annoying than having to pull > up the keyboard when I want it. There are many times that a program will > automatically put the cursor into a text field, and I don't want to do > anything with that text field, so I have to manually close the keyboard. > Then I click somewhere else on the screen, and it happens to go into a text > area again... the keyboard auto-displays, and I have to manually close it > again. > > Is there a configuration that I can tell it to only display and hide > manually? I want it to stay invisible until I want it, and I want it to > stay visible until I'm done... indicated by hitting the button to activate / > deactivate. I don't want it to try to interpret when it thinks I want it > and when I don't. > > I've searched the mailing list using Nabble, and the only thing I found was > from when the matchbox keyboard was a separate application, and there was a > separate configuration (/etc/matchbox/session). Unfortunately that path > doesn't exist in the December release. > > Thanks for any info. > > -Laura > -- > View this message in context: http://n2.nabble.com/SHR-U-Stop-keyboard-auto-display-tp4256334p4256334.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > _______________________________________________ > Openmoko community mailing list > [hidden email] > http://lists.openmoko.org/mailman/listinfo/community > That's matchbox-keyboard-im which makes keyboard popping up automatically with GTK+ apps (don't be suggested with name, on default install matchbox-keyboard-im pops up Illume keyboard ;)). You can uninstall that package. -- Sebastian Krzyszkowiak dos _______________________________________________ Openmoko community mailing list [hidden email] http://lists.openmoko.org/mailman/listinfo/community |
Ok, that worked for GTK+ apps, but what about the rest of them? There are text fields in the settings python apps that if you touch the wrong area, the keyboard still auto-displays. Is there any way to stop it there as well? Even if it can't, the fact that it's stopped in GTK+ apps is very helpful, so thank you very much for that. :) -Laura |
|
I recently did an update / upgrade, and I've notice that the problem is back, but more stupid.
I removed the package again (matchbox-keyboard-im), and the package that depended on it but provided no files ("opkg files" showed the package name, but nothing in the list). I suppose that package was simply added to create a dependency on the other package. The complaint I had in non-GTK apps is still there, but now it's more severe. Any time I close an app such as the power settings, the keyboard has to pop up because of that click and it stays visible on the settings page even though there are absolutely no entry fields. In fact, almost any time I click a Python button, the keyboard appears. In the messages (SMS) app, if I'm going through and deleting my old messages, the keyboard pops up every time I click "Options" so I have to wait for the screen to redraw. Then the keyboard stays there regardless of the fact that there is nothing that allows text entry on that screen. Why does it seem that the keyboard is being forced to be more obtrusive when I want it to be less obtrusive? If there were some kind of setting that I could turn off, I'd be happy, but there's nothing. Maybe a lot of people like the keyboard popping up when you don't want it (and in places where you can't even use it), but I'm not one of those. |
|
That's bug, not intended behaviour. Just wait for fix for that.
On 1/27/10, vancel35 <[hidden email]> wrote: > > I recently did an update / upgrade, and I've notice that the problem is > back, > but more stupid. > > I removed the package again (matchbox-keyboard-im), and the package that > depended on it but provided no files ("opkg files" showed the package name, > but nothing in the list). I suppose that package was simply added to create > a dependency on the other package. > > The complaint I had in non-GTK apps is still there, but now it's more > severe. Any time I close an app such as the power settings, the keyboard > has to pop up because of that click and it stays visible on the settings > page even though there are absolutely no entry fields. In fact, almost any > time I click a Python button, the keyboard appears. > > In the messages (SMS) app, if I'm going through and deleting my old > messages, the keyboard pops up every time I click "Options" so I have to > wait for the screen to redraw. Then the keyboard stays there regardless of > the fact that there is nothing that allows text entry on that screen. > > Why does it seem that the keyboard is being forced to be more obtrusive when > I want it to be less obtrusive? If there were some kind of setting that I > could turn off, I'd be happy, but there's nothing. > > Maybe a lot of people like the keyboard popping up when you don't want it > (and in places where you can't even use it), but I'm not one of those. > -- > View this message in context: > http://n2.nabble.com/SHR-U-Stop-keyboard-auto-display-tp4256334p4468921.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > _______________________________________________ > Openmoko community mailing list > [hidden email] > http://lists.openmoko.org/mailman/listinfo/community > -- Sebastian Krzyszkowiak dos _______________________________________________ Openmoko community mailing list [hidden email] http://lists.openmoko.org/mailman/listinfo/community |
| Powered by Nabble | Edit this page |
