> You can certainly mix Qt with Wt but the SLOT macro is a nuisance. > > For Wt the SLOT macro does not really do anything, and you can safely > replace "connect(SLOT(a, b))" with "connect(a, &b)". Ironically, we > initially though the macro would be a good idea to make Qt developers > feel at home, but they are the ones mostly affected by it being there > ! > > The next release of Wt will provide a define -DWT_NO_SLOT_MACRO which > does not try to define the SLOT/slots/signals macro's. > Until then you will need to undefine the SLOT (and signals/slots) > macro as in the wtwithqt example's QtObject.h before including Qt > header files. > > Regards, > koen
Hi koen, why not call the macro WSLOT instead and add a define for backwards compatibilty. As everything else in Wt is prefixed with W. Just my thoughts Regards ......Volker ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
