Re: issues with input module that creates a window

On Sat, 2003-03-29 at 17:53, Noah Levitt wrote:
> Hi,
> I'm working on a gucharmap input module and I've run into
> some issues.
> When the user picks imgucharmap from the list of input
> methods, a gucharmap window opens. The problem seems to be
> that the window has an editable inside it, so another
> gucharmap window opens as the input module for that
> editable, and so on recursively, ad infinitum.
> Looking through the gtk+ source, I don't see a way to
> programmatically set the active input module on a widget. Is
> there a way?
> A possible solution would be to not immediately pop up a
> gucharmap window, but wait until the user presses (say)
> shift+space.  But I think that's a surefire way to make sure
> no one ever figures out how to use it.
> A couple of other less pressing questions. 
>  - Assuming I don't do the shift+space thing, what should I
>    do when the gucharmap window is closed, with alt-f4 for
>    example?
>  - Which window type hints would be appropriate for the
>    gucharmap window?
> Also, if anybody knows of another gtk+ input module that
> opens a window, I'd like to look at it to get ideas.

Unfortunately, I think this is probably a misuse of
GtkIMContext ... is the user going to figure out that
to start typing text again in any entries they have to
use the right click menu to switch back to the Default
input method? (Or in some locales, X Input Method) 

I don't think the GtkIMContext can really be used without
modification as "insert special character". If we want stuff
like that, I think we'd need a special facility.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]