Re: g_signal_parse_name



On Thu, 14 Dec 2000, James Henstridge wrote:

> I was fixing my python bindings to handle signal details correctly.  This
> involved using g_signal_parse_name in place of g_signal_lookup.  This
> function is marked private in the header, but it seems to be the only way
> to parse out the detail portion of a string.  Is this function really
> meant to be private?

erm no, i exposed that so you can actually use it in your bindings ;)

that reminds me, gtksignal.c needs to use g_signal_parse_name() as well to
get details for gtk_signal_connect() and friends right (if anyone wants to
tckle this and send me a patch, that'd be apprechiated).

> 
> James.
> 

---
ciaoTJ





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]