Viktor Szakáts wrote:
>
> Anyhow it again shows very grave problems with HBQT.
>
> No sort of missing file, or volatile environment
> property/error (or user action) should ever cause
> a GPF.
>
> Looks like nobody is really bothered by these, and
> sorry to repeat, but it makes the whole package
> unsuitable for any sort of professional work. It's
> difficult to trust a codebase where such GPF's
> are consistently unfixed for months, and if fixed,
> only worked around on the UI level.
>
> Or it's possible I'm wrong, and GPFs are normal
> fact of life in GUI-world.
>
It is a programming fact on the surface to cover
some of the unwanted side-effects of Qt which I do not yet
how they should be implemented in a way that does not
cause GPF.
I am constantly struggling to find the solution.
But seems my meagre knowledge in CPP space is really
restrictive in this effort.
Nevertheless, the struggle is on. We found many solutions
in the past and we will find many in the future. Hatbour-Qt
is evolving, still.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/SF-net-SVN-harbour-project-13957-trunk-harbour-tp4611158p4613679.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
