Re: Language bindings and popup_menu and show_help signals

[Yevgen Muntyan <muntyan tamu edu>]

Owen Taylor wrote:

> Please don't bind all keybinding signals. You are just asking for
> problems (as you discovered) if you bind them, and, perhaps worse,
> they pollute the API and confuse users...  see for instance,
> GtkTextView::move-cursor... 
But if it's not wrapped, binding user won't be able to override
the default handlers.  GtkTextView::move-cursor is an example
of a signal where overriding is useful - e.g. for customizing moving
cursor by words.

> users think they are change notification
> and get confused when they don't always get called.
>  
The solution for this problem is documentation which would tell
what signal does and when to use or not to use it. "it might confuse
someone" is not a reason to limit *functionality*.

> I think you have to figure out ad-hoc what signals need to be bound
> for connection/overriding and when it isn't clear from the docs, file
> bugs.
>  
If a signal has class method, then it is supposed it may be overridden
in subclasses, isn't it? There is _gtk_binding_signal_new, that may be
used, or header must say "you may not override it", or something; but
by default if a signal is public, it must be public and must be in bindings.

Best regards,
Yevgen