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 38670 - Selected input method should be per-toplevel?
Selected input method should be per-toplevel?
Status: RESOLVED DUPLICATE of bug 50629
Product: gtk+
Classification: Platform
Component: Input Methods
1.3.x
Other other
: Normal enhancement
: future
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2001-01-25 17:45 UTC by yzhang
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description yzhang 2001-01-27 19:49:05 UTC
Package: gtk+
Version: 2.0

OS: RedHat Linux 6.2
X: XFree86 3.3.6
C: glibc 2.1.3

How to reproduce the bug:

Compile and run gtk+/examples/filesel/filesel.  Click on
Selection entry, change input method to "Cyrillic" and
type "abc" for example.  Then Click on Change Dir button
and type "cde" in Directory name entry.  Now change input
method back to "Default" for Directory name entry, so far
so good.

When click back on Selection entry,  the following message
is showing on terminal:

GRuntime-Message: finalizing GObjectClass `GtkIMContextCyrillicTranslit'

GRuntime-Message: finallizing base class of GtkIMContextCyrillicTranslit

But the input method of Selection entry should still remain in
Cyrillic but it failed if typing anything in it.  The error message
is:

** CRITICAL **: file pango-layout.c: line 1455
(pango_layout_get_cursor_pos): assertion `index >= 0 && index <=
layout->length' failed

Question:

What is the proper behavior of input method change when
switching windows?  It is desirable that whatever the original
input method should be re-activated for the windown and
works as if the user has never leave the window.




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 14:49 -------
This bug was previously known as bug 38670 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=38670
Originally filed under the gtk+ product and general component.

The original reporter (yzhang@sharemedia.com) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, gtk-bugs@gtk.org.

Comment 1 Owen Taylor 2001-06-01 15:16:08 UTC
The change in input method is meant to be global. I'm not sure
what is going one with the errors you are seeing.
Comment 2 Owen Taylor 2001-12-12 22:38:09 UTC
Wed Dec 12 17:22:45 2001  Owen Taylor  <otaylor@redhat.com>

        * gtk/gtkimmulticontext.c (gtk_im_multicontext_set_slave):
        Reset the existing slave before removing it to give
        it a chance to commit and emit "preedit_changed" 
        in case there was still a preedit string.

Fixes the crashes. See #66286 for a note a possible bug that
is related to this fix. Leaving it open as a suggestion
that the selected input method should be per toplevel
(or per widget?) rather than global to the app. [ Big questions here
about how it should  behave across the desktop, since users
aren't usually aware of what toplevels belong to what app.
Comment 3 Owen Taylor 2002-09-06 16:54:49 UTC
Moving input method related bugs to input-methods component
Comment 4 Matthias Clasen 2003-05-05 10:33:11 UTC

*** This bug has been marked as a duplicate of 50629 ***