GNOME Bugzilla – Bug 735462
There's no such thing as a private Q_PROPERTY
Last modified: 2014-12-25 16:03:40 UTC
In Qt, the Q_PROPERTY macro is an empty macro that is used only by moc. The macro declares a *public* property. It doesn't matter whether it appears in the private, protected, or public sections of the class - the property is always public. This is a regression from 1.8.7, most likely caused by the fix to bug 734245. For example, taken from qobject.h from Qt 5: class Q_CORE_EXPORT QObject { Q_OBJECT Q_PROPERTY(QString objectName READ objectName WRITE setObjectName NOTIFY objectNameChanged) ... }; This declares a *public* property, in spite of appearing in a private section of the class. Neither does this macro change the visibility of the succeeding members: its expansion is empty. It's not like the Q_OBJECT macro which *does* change the visibility of the succeeding members to private.
Confirmed. Should be fixed in the next GIT update.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.9. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant (preferrably in the form of a self-contained example).