Nickolai Dobrynin wrote:
> Thanks for your input. It looks like the obvious way of getting around the
> default signal handler for "toggle_overwrite" is by using
> 'g_signal_connect_after'. This is *A* way of dealing with that. However,
> is it possible to completely drop the default handler so
Paul,
Thanks for your input. It looks like the obvious way of getting around the
default signal handler for "toggle_overwrite" is by using
'g_signal_connect_after'. This is *A* way of dealing with that. However,
is it possible to completely drop the default handler so it wouldn't even be
around
Nickolai Dobrynin wrote:
> Paul,
>
> > But do you really need to do that? Most users (AFAIK) never use
> > overwrite mode, but those who do will be confused with your application.
>
> It's the users who've demanded that feature. The very nature of the
> application
> is odd. It involves enter
Paul,
But do you really need to do that? Most users (AFAIK) never use
> overwrite mode, but those who do will be confused with your application.
>
It's the users who've demanded that feature. The very nature of the
application
is odd. It involves entering a lot of financial data in realtime.
Nickolai Dobrynin wrote:
> I was wondering if there is a way to make it so that the text that gets
> typed into
> the GtkEntry widget is always *inserted* into it and never replaces whatever
> was previously
> entered. In other words, is it possible to suppress the "Insert" key so
> that the overw
I was wondering if there is a way to make it so that the text that gets
typed into
the GtkEntry widget is always *inserted* into it and never replaces whatever
was previously
entered. In other words, is it possible to suppress the "Insert" key so
that the overwrite mode
could never be entered into
