Hi Przemek, > Returning to your problem with GTK. When exactly the problem appears? > After RT error? Is it GTK bug or it's necessary to close Harbour > application without closing GTK. If you say sth more maybe I can help.
I think that's not related to harbour, because harbour close the application gracefully. The issue happens with Gtk itself, when some invalid pointer is handled or some unknown condition, I couldn't identify that condition, it just abort the gtk app, so it means that it exits the gtk main loop, without call the previous GCNotifyClosure ones. One case that I've here is related to the gtk_operation_new(). It's for all signed callbacks to call the function on g_signal_connect_data(), but specific to this function. I don't know why, but I'm working with some gtk people to see if is some sort of gtk bug or not. Thanks anyway, I'm just wondering some way to use a better approach regarding the gtk callbacks and harbour, instead of rely on GCNotifyClosure do free up the items allocated by hb_itemNew(). Maybe create a stack list and then clean up those that weren't freed properly, etc... Thanks Rodrigo _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
