Just hold on. Your point is valid. For that to happen we need
more insght how Qt works. This is first step in that direction.
First I have to get rid of memory consumption.
Next I will go for modularity. I wll explain why that could not been
achieved so far. For sure final result will be far superior.
OR can you suggest the skeleton of modularity in this scenario ?
I can only suggest the skeleton which we use in all
GC scenarios in Harbour, this means separate GC pointer
creator and release functions for every possible objects.
This would mean the addition of 2 extra C level functions
(one called directly, the other the release callback)
inside each .qth/.cpp functions implementing the QT objects.
But I don't know why that didn't work for you in case
of QT, so I can't suggest anything else this time.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
