maemo.org Bugzilla – Bug 1163
GtkCellRendererText: Can not edit with virtual keyboard
Last modified: 2010-03-15 20:53:10 UTC
You need to
before you can comment on or make changes to this bug.
(Extracted from bug 1154)
See attachment 254 [details] for testcase.
1. If you edit any TreeView row, you can change the text with the keyboard, but
not with the large thumb-board. The text appears to be modified, but when the
thumb-board goes away, the text remains the same.
I've seen this on maemopad+ todo lists as well. Over to input methods.
Put Tomas in Cc.
I am also experiencing this problem with applications like Maemopad+ and Todo.
It is really annoying.
Oh, and the "paste" function of the on-screen keyboard also doesn't work.
I suspect the problem is that when the cellrenderertext loses focus (which is
the case when using "paste" form the on-screen keyboard or opening the thumb
keyboard), it won't be editable anymore.
Can you please post the exact software version you are running (please also
make sure it is the latest) (Control Panel > General > About product)?
Hmm, a pygtk testcase... We don't officially support python... :-/
It's not pygtk-related. It's gtk-related (and therefore also affects pygtk
"Product info" screen gives:
Internet Tablet OS: maemo Linux based OS2008
+ my Bluetooth and W-LAN MAC addresses
How can I trigger this issue in Maemopad+?
(In reply to comment #7)
> How can I trigger this issue in Maemopad+?
1. Create a new "checklist" node
2. Add a new checklist item
3. Click on the checklist item to edit its text
(Now, if you use the on-screen stylus keyboard [the small one on the bottom of
the screen], this works, but..)
4. Click with the middle button of the d-pad to open the finger keyboard
5. Enter some text
6. See that the focus of the widget has been removed when the finger keyboard
has appeared, and therefore the text is not changed
If you need anything else, please tell me and I'll happily provide you with the
(In reply to comment #8)
> (Now, if you use the on-screen stylus keyboard
> 4. Click with the middle button of the d-pad
Sounds like N800 that I don't have. :-/
Ah. Confirming. N810:
1. Create a new checklist item in the right pane
2. have the physical keyboard not available
3. Xlick twice into the checklist item
4. The fullscreen keyboard appears.
5. Enter some text and use either the ⤶ or ⤓ button.
Text is lost.
Bug 4057 might be a duplicate.
Now if the Python deps would be sorted out for Fremantle this could be tested
again in Scratchbox against Fremantle... :-/
Hi, any testcase for Fremantle? Looks like Maemopad+ is not available yet...
Created an attachment (id=1354) [details]
(In reply to comment #12)
> Hi, any testcase for Fremantle? Looks like Maemopad+ is not available yet...
Attached you'll find a minimal testcase (tested only on Diablo on a N810,
because the Fremantle SDK does not have the full-screen virtual keyboard - at
least I was not able to bring it up).
How to reproduce (again, on Diablo; should be the same on Fremantle, though):
1.) Copy testcase1163.py to your device
2.) Open xterm and "cd" into the download folder
3.) Enter command: python testcase1163.py
4.) Double-click (touch) on the "test" row to start editing
5.) Tap in the edit field until the fullscreen keyboard opens up
6.) Edit the text and hit "Enter" (or the "hide keyboard" button)
Expected: Text is edited
Actual outcome: Text is not edited
Again, I suspect that the reason for this bug is that the treeview/cell loses
focus (and therefore editing stops) when the full-screen keyboard is opened.
If test cases exists, should we file a bug against Fremantle?
Oops, seems like I missed Thomas' comment 13.
Confirming - still an issue.
Thomas: Does this also happen when linking against both gtk+ and hildon?
(In reply to comment #16)
> Thomas: Does this also happen when linking against both gtk+ and hildon?
With the Python script, I don't "link" to any libraries (at least not in the C
sense of linking in libraries, which is what I think you mean).
I suppose pygtk on Maemo is linked against the hildon version of GTK+ if you
mean that, but I honestly don't know. The PyMaemo guys should know an answer to
This has been fixed in package
which is part of the internal build version
(Note: 2009 is the year, and the number after is the week.)
A future public update released with the year/week later than this internal
build version will include the fix. (This is not always already the next public
Please verify that this new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
To answer popular followup questions:
* Nokia does not announce release dates of public updates in advance.
* There is currently no access to these internal, non-public build versions.
A Brainstorm proposal to change this exists at
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).