Todd Weiler wrote: > Hi Gunnar > > Ok - setQProperty was a bad idea. > > Thank you for finding that bug in the groovy bug system - I'm > embarrassed I didn't check there myself. I hope that they will be able > to deal with the issue.
Its scheduled for fixing in 1.5.7 and 1.6-beta2 according to the update I got. > 1. setProperty IS generic as you mentioned - those not used to using > dynamic properties may skip over this feature never realizing it's power > - my first thought was that it was just a different way to set existing > properties of an object, possibly put there to accommodate different > programming styles setProperty sets both dynamic properties (non-setX/x()) and normal properties, so I feel the name is correct. The point is maybe that there are no examples on this and the there could be better documentation? - Gunnar _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
