>> 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.
If these are ever just masked, we'll have an infinite amount of reports in the future when the same thing reappears again and again at random times. We also don't know if these are new issues or unfixed old ones. To ever get these covered, I think each such cases should be replicated using an isolated (self-contained) test case, so that we can give it a closer look and make the real fix eventually. Such test cases can be stored in /contrib/hbqt/tests/ directory for reference. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
