Closed GoogleCodeExporter closed 9 years ago
I've been able to reproduce it, apparently this happens when suggestions are
turned off where it's not supposed to show the underlining. It is normally used
to indicate the current word in suggestions mode.
As far as I can tell this is harmless, please let me know if it's causing any
problems other than temporarily showing underlines. I plan to fix it anyway,
just want to know if it's an urgent issue.
Original comment by Klaus.We...@gmail.com
on 26 Feb 2012 at 7:21
Please try v1.32rc1 (or later) from
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that
fixes it for you.
Original comment by Klaus.We...@gmail.com
on 26 Feb 2012 at 10:39
Works like a charm, Klaus ;) tested in openoffice and various text editors,
gmail, gtalk and browsers. Thanks for the quick fix, its an amazing keyboard
and your response is the tops ;)
Original comment by mslour...@gmail.com
on 27 Feb 2012 at 3:58
Thanks for testing. I made this build via ConnectBot on my phone, so the
testing may have been a bit less rigorous than usual on my part :-)
(For reference: revision b87fcf8bb47c)
Original comment by Klaus.We...@gmail.com
on 27 Feb 2012 at 8:03
[bulk bug update]
The changes from the 1.32rcX prerelease series are included in version 1.33 as
published on the Play Store, and this bug should be fixed. If it's still not
working for you, please reopen or file a new bug. Thanks to everyone who helped
with finding bugs and testing!
Original comment by Klaus.We...@gmail.com
on 3 Jul 2012 at 7:24
Bulk update - changing "Fixed" to "Verified" for old bugs.
(Background: I'm changing the "Fixed" status to be considered open, the next
steps in the lifecycle will be the closed states "FixInTest" and "Verified".
This lets me mark issues as "Fixed" in commit messages without hiding them from
the issue tracker.)
Original comment by Klaus.We...@gmail.com
on 22 Jan 2013 at 7:33
Bulk update - changing "Fixed" to "Verified" for old bugs.
Original comment by Klaus.We...@gmail.com
on 22 Jan 2013 at 7:34
Original issue reported on code.google.com by
mslour...@gmail.com
on 26 Feb 2012 at 5:29