What's the benefit of not generating it on the C++ level? I mean, I understand you _can_ do that, but I don't quite see why you would prefer to introduce an inconsistency like that?
QML will need a notification signal if we remove support for bindables and Robert wants to search-replace his properties that only have a bindable. I could force him to write an extra signal into the header for each of his properties but he won't like that. The other solution is to have moc generate a metaobject-only signal via a special directive for QML to use. There is precedence for the "default" already. We have it for WRITE at least.
best, Ulf -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
