>> Is it be possible to add slots and events holder variables >> to QApplication class? If technically possible, IMO it should >> be done to clean this part of QT. It wouldn't even be >> an incompatible change, just convenience, since these >> two holders are always needed for QT apps. >> > > Perhaps not. > > The reason is, we need to manipulate this mechanism > on thread level, which, at this moment, is not mature unfortunately. > But I do not want to rob-off this possibility in any way. > > Moreover, slots can be initiated per class instance basis > which is a big productivity boost. In a super class we > can initialize it without the intervention of the user and can > designate a destructor and as such it will be managed by the > class object. > > Events, however, are different beast, have to be controlled > centralized. But still in that case, I cannot imagine how we > can attach to QApplication under the scenario it is > implemented currently.
Perhaps: VAR events // in QApplication instead of: STATIC s_events Former is much cleaner. QApplication class seems to be a requirement for any HBQT app so it seems doable. Anyway just ignore this like most other suggestions from me. For me it's not a problem. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
