After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 643439 - Need undo/redo methods for GtkIMContext
Need undo/redo methods for GtkIMContext
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Input Methods
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-02-28 01:12 UTC by Hiroyuki Ikezoe
Modified: 2018-04-15 00:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
First proposal (4.60 KB, patch)
2011-02-28 01:12 UTC, Hiroyuki Ikezoe
none Details | Review

Description Hiroyuki Ikezoe 2011-02-28 01:12:40 UTC
Created attachment 182061 [details] [review]
First proposal

Given that undo button is pressed while preediting, we need undo/redo methods for GtkIMContext since each input method only knows about the last operation in the input method.

For example in gedit with Japanese input method,

1. Input "1234" directly
2. Input "asuha" through Japanese input method at the tail of "1234"
3. Then gedit shows 1233[あすは]
  [] means preedit string here.
4. Convert "あすは" to "明日は" (not commit yet at this time) 
5. Press undo button

Actually gedit delete "1234" string and leave [明日は] as it is, but users expect to be revert the conversion. i.e. gedit should show 1234[あすは].
Comment 1 Matthias Clasen 2018-02-10 04:57:33 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:04:34 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new