|
From: Chris F. <cd...@fo...> - 2011-05-22 07:02:45
|
On Sat, May 21, 2011 at 06:30:17PM -0300, Luiz Angelo Daros de Luca wrote: > Now, I faced a problem. I use osync_plugin_set_data to save ruby context > callback functions for initialize,discover,finalize callbacks. > ObjectTypeSink also need some callbacks, which are paticular for each Sink > type. However, the same solution is not possible because even if I can > osync_objtype_sink_set_userdata, I cannot get it back because I have no > exported osync_objtype_sink_get_userdata. I can write some hack to get a > individual userdata callback functions save but this is not really what I > want. So, I have some questions: > > 1) Turning osync_objtype_sink_get_userdata into a private method was > intentional? > 2) Is there a real reason for that? > 3) Am I doing something wrong? I think the idea was that the userdata, as well as the OSyncObjTypeSink pointer is passed back as arguments to all the sink callback functions anyway, so there's no need to retrieve it with an explicit function call. Do you need this user data from outside the callback functions? - Chris |