[Glade-users] handler_ids

[Tristan Van Berkom]

Signals in Glade need work in order to be useful, if you want to rally
an effort to that effect, I would suggest filing some bugs to Glade
and GtkBuilder.

  - As you mention, you cant retrieve the connection handler id
  - A big problem is that user data is pointless unless you pass it
    an object (cant use integers or strings in user data, nor pass it
    the pointer to your UI controller object).
  - Libglade offered glade_xml_signal_connect() to explicitly connect
    signals to implicitly built objects, my opinion is this was the
    best practice using libglade (i.e. avoid autoconnecting), but I see
    no current builder equivalent in place.

So, you could file those bugs against GtkBuilder, maybe get the
GTK+ boys interested and think up some cool features to do along
those lines... and hopefully something will be done... by
somebody ;-)

Cheers,
                     -Tristan



On Fri, Mar 13, 2009 at 9:52 AM, Peyman <peter.peyman.puk at googlemail.com> wrote:
> Hello Tristan
>
> I didn't see this e-mail, but Walter gave me the same advice over on the
> pyGtk forum.
>
> I don't see why glade doesn't provide this functionality seeing as it would
> be very easy to provide a dictionary item with the handler_ids. Is there a
> reason why signal_autoconnect does not do this?
>
> Cheers
>
>
> Peyman Askari
>
> On 11 Mar 2009, at 14:02, Tristan Van Berkom wrote:
>
>> On Wed, Mar 11, 2009 at 9:06 AM, Peyman <paskari007 at yahoo.ca> wrote:
>>>
>>> Hello
>>>
>>> I am trying to call handler_block/handler_unblock, but I am having
>>> problems locating the handler_ids. This is b/c glade calls
>>> "connect()", which is the method which returns the hander_ids. Does
>>> glade provide a dictionary for retrieving these ids?
>>
>> Currently no, builder - like libglade did, will just connect the signals.
>>
>> You can use g_signal_handler_block_by_func() though.
>>
>> Cheers,
>>                  -Tristan
>
>