Re: issues with input module that creates a window

[Noah Levitt <nlevitt columbia edu>]

Hi,

This is pretty late, I know, but in case you're interested.
I took Owen's advice and create one window which I remember
using g_object_set_data (gdk_display_get_default (), ...),
and never create a second window.

I skimmed the other thread on gtk-list about problems with
the module being unloaded and static variables being reset.
I took the easy route and made the module permanently
resident once it's loaded:

const gchar * 
g_module_check_init (GModule *module)
{
  g_module_make_resident (module);
  return NULL;
}

If this is bad, please advise. It seems to work ok.

Noah

On Sun, Mar 30, 2003 at 14:47:59 +0800, James Su wrote:
> Hi,
> I met this problem too! I'm developing a im module for gtk+2.x which 
> will popup a window with a non-editable Editable widget, but I failed 
> with the same problem. Finally I fork a new widget from Editable widget 
> which get rid off all of the input method code and solve the problem.
> I also want to know if there is easier way to solve such problem by 
> disabling or specifying the input method of an Editable like widget.
> 
> Regards
> James Su
> 
>