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
Hi Przemek,
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.
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.
Thanks
Rod
On Thu, 27 Nov 2008, Rodrigo Miguel wrote:
Hi Rodrigo,
> 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 ab
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
applicat
On Thu, 27 Nov 2008, Rodrigo Miguel wrote:
Hi Rodrigo,
> I'm facing in some rare cases the "Warning, memory allocated but not
> released: 1124 bytes (16 block(s))" due to the unfreed allocate HB
> ITEM. For some unknown reason, when gtk is terminated abnormally, it
> doesn't call the gc closure n
Hello All,
I'm facing in some rare cases the "Warning, memory allocated but not
released: 1124 bytes (16 block(s))" due to the unfreed allocate HB
ITEM. For some unknown reason, when gtk is terminated abnormally, it
doesn't call the gc closure notify. Here are some examples that I'm
using for:
v
