Hi Pritpal, >> This in turn means that the original high expectations >> for HBQT becoming "the" GUI for Harbour are vanishing. >> >> Given the effort put into this and the importance of >> a GUI in general, this is a pity. >> > > I agree with all your assertions in toto. > > But the bottom-line is, I am unable to find a solution > to coordinate when Qt destroys an object and when > Harbour request it to destroy. > > Unless someone more gifted join this effort, > like Istavin tried and offered some constructs, I do not > see much progress. Time-and-again I try with a new > concept, but at points it fails. The current implementation > is the best so far.
Easy to say it, but since you probably know the typical cases that need to be covered, so maybe it'd help to start off with a very limited set of wrappers, just to cook the right wrapping methods. For sure you'll need to employ the concept of GC references. Without it, it will never be right. It would also help just by itself, if you could create self-contained examples of the typical construct/destruct/detach/attach situations. This would make it easy for everyone to experiment with it in a swift fashion (without dealing with the huge HBQT libs). Just an idea. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
