On Thu, 27 Nov 2008, Rodrigo Miguel wrote: Hi Rodrigo,
> Sure, I'll talk with other xhgtk developers and do a task force to > validate all parameters being passed and return the appropriate RT > Error. If you will have any questions about Harbour internals then I'll try to help. I do not think I have enough knowledge about GTK to help, for sure you know about it much more. GC collectible pointer items have yet another feature. You can associate destructor with them. So when variable which holds it will be out of scope or cleared then GTK resources will be automatically freed. Please also consider that it may force using g_object_*ref() to play fairly with GTK internals. Where is should be used and how it's a decision for someone who well knows GTK and xhgtk. > By the way, I found the issue with g_signal_connect_data & > gtk_opertaion... I need do a g_object_unref once I get done the > printing. Good news. I do not know the details but it's possible that with automatic destructors it will not be necessary. It depends on context. If it's possible it's good to hide such functions from .prg interface: one possible resource leak less. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
