GNOME Bugzilla – Bug 542340
Default signal name
Last modified: 2009-01-21 01:22:45 UTC
It allows anjuta to get the most commonly used signal name for making appropriate stub easily e.g. by double click.
Created attachment 114298 [details] [review] Default signal name support
Created attachment 114342 [details] [review] The patch doesn't depend on 111685
Ok I like the idea, I havent been through all your patches yet, does the signal editor in glade use this metadata somehow ? if we do add this metadata, Id like you to add it in the <signals> scope, somewhere around gwa_set_signals_from_node() maybe more like: <signals> <signal id="clicked" since="2.0" default="True"/> <signal...> </signals>
> does the signal editor in glade use this metadata somehow ? The answer is "no", so I think it would be better to hardcode default signals into anjuta plugin until somebody will find a good idea of using it in glade.
Pavel, can you take care of this? This is the last blocker for inclusion of the new glade plugin.
(In reply to comment #5) > Pavel, can you take care of this? This is the last blocker for inclusion of the > new glade plugin. > Sure!