[Development] Qt Namespace enums defined in QTextDocument

lars.knoll at nokia.com lars.knoll at nokia.com
Sun Mar 25 23:28:29 CEST 2012


Longer term, I think we should have one qmoduleglobal.h per shared library, and have the additional enums in there. Nothing speaks against them living in the same namespace though IMO, but we'll need to sort out how qdoc handles this.

One idea might be to handle the namespace similar to inheritance, i.e. the Qt namespace in QtGui "inherits" the one from QtCore.

Cheers,
Lars


From: "ext casper.vandonderen at nokia.com<mailto:casper.vandonderen at nokia.com>" <casper.vandonderen at nokia.com<mailto:casper.vandonderen at nokia.com>>
Date: Sun, 25 Mar 2012 10:12:29 +0000
To: <development at qt-project.org<mailto:development at qt-project.org>>
Subject: [Development] Qt Namespace enums defined in QTextDocument

Hi,

The Qt::HitTestAccuracy and Qt::WhiteSpaceMode enum are defined in QTextDocument (which is in QtGUI), but they are documented in the Qt Namespace, which is in QtCore.
This obviously does not work if we want to modularize the documentation on a library level.

I have no idea how to solve this in an easy way,  maybe we could do multiple runs on QtCore documentation (QtCore -> QtGUI -> QtCore), but that is not what I would like to do. Any ideas?


Casper
_______________________________________________ Development mailing list Development at qt-project.org<mailto:Development at qt-project.org> http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120325/4d0fbf57/attachment.html>


More information about the Development mailing list