>> "ToOutDebug" and friends are not allowed to be used in
>> any of our contribs. Ever. Yet they are unfortunately.
>> There is a large inconsistent mess when it comes to debug
>> calls in hbqt/hbxbp.
>>
>
> But then there is no viable alternative to this until library stabilizes.
> I think we
Hi
Bisz István wrote:
>
> The modified hbqt, hbxbp, demoqt and demoxbp are now crash free on Windows
> Vista with Mingw, Fedora12 and CentOS5.4. The log-s produced by valgrind
> on linux are clean.
>
Good to know.
It is not a only matter of crashes when exiting the application,
More concern
Hello
Viktor Szakáts wrote:
>
> "ToOutDebug" and friends are not allowed to be used in
> any of our contribs. Ever. Yet they are unfortunately.
> There is a large inconsistent mess when it comes to debug
> calls in hbqt/hbxbp.
>
But then there is no viable alternative to this until library
...@harbour-project.org] On Behalf Of Pritpal Bedi
Sent: 2009. november 13. 0:18
To: harbour@harbour-project.org
Subject: Re: [Harbour] HBQT, HBXBP - Test - New HB GC and QT interface
Thanks Bisz
Bisz István wrote:
>
> Please find attached the HBQT and HBXBP components modified to eli
"ToOutDebug" and friends are not allowed to be used in
any of our contribs. Ever. Yet they are unfortunately.
There is a large inconsistent mess when it comes to debug
calls in hbqt/hbxbp.
At the same time I've added this in hbxbp on .prg level:
---
#if defined( __HB_OUTDEBUG__ )
Thanks Bisz
Bisz István wrote:
>
> Please find attached the HBQT and HBXBP components modified to eliminate
> the
> crashes already reported on this list.
>
> ·The main modification is in the HB GC and QT interface,
> eliminating
> the crashes caused by the double object deletes. The m
