Re: Need new name for connect_object()

A - I see your point. I've never had a call yet to come up with the simple version, so I didn't even think of it. But, based on the past few months, it's probably out there, waiting, in my future. So, I guess my vote would be for 3 different ones - for clarity's sake. Madeleine D. At 01:02 PM 3/21/05 -0800, you wrote: >Not really. What it does currently is "omit" the signal object, passes >the rest of parameters, adding on the user specified-ones at the end. >So, if originally the parameters to be passed were ($signal_widget, >$col, $row), and we connect it as: > >$w->connect_object('foo', 'myfoo', $myobj); > >the parameters it'll pass are ($col, $row, $myobj). > >I guess what I am asking is whether this behavior is useful at all, or >if we would rather really substitute the user specified object instead >of the signal one, or not pass any signal parameters at all, or what. >Or maybe have a connection function for all three cases: > >1) connect normally: pass signal widget plus additional signal-specific >parameters >2) connect replace: substitute user-specified object instead of the >signal one, and pass additional signal-specific parameters >3) connect simple: pass only user specified parameters > >-Andrei > >On Mar 21, 2005, at 11:29 AM, Madeleine D. wrote: > >> I'm probably being too simplistic here, but what about >> >> connect_other() >> >> since it does the same things as connect, including parms, but it does >> it >> for another object. >> >> Madeleine D. >> > >