This question already has answers here:
Exclude some classes from doxygen documentation
(3 answers)
Closed 4 years ago.
I'm documenting a project built in Qt using doxygen, my problem is that classes and structures from Qt such as QString is being documented.
I want to exclude all QString types from my documentation and only keep the ones i declare and implement.
I know that this should be done some way in the doxyfile, but i have no idea how to do it. Any idea??
Thanks in advance.
Use the doxygen exclude property:
http://www.doxygen.nl/manual/faq.html
Related
This question already has an answer here:
//! [0] in Qt source code
(1 answer)
Closed 6 years ago.
While looking through Quick Controls 2.0 sources, I came upon a peculiar comment syntax that I can't seem to find in docs:
//! [property]
property: ...
...
//! [property]
for example, pairs of //! [contentItem], //! [background] could be seen in TabButton.qml.
I wonder if this is just a convention chosen by the developers to delimit regions of code, or does it indeed have some special meaning?
With Qt comments that begin with ! are parsed to generate documentation. That applies to single and multi line comments.
In this particular case however it doesn't seem to contain any actual documentation, it is used to signify the lines where individual implementation details begin and end.
You can learn more about the documentation format here.
There used to be example code snippets on the Customizing Qt Quick Controls documentation page, that were automatically extracted from our own QML code with help of those qdoc-markers.
This question already exists:
Closed 10 years ago.
Possible Duplicate:
How to include additional compiler options“includes” and “include-libraries”?
I want to include in my flex project a custom package that contains hundreds of fxg objects using the additional compiler options. Which specific option can i use an how i should I declare?
-includes for MXMLC and -includes-classes for COMPC.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Find Unused Resources in a .NET Solution
In a webapplication we have a lot of images and some of them are not used/referenced anymore. Is there way (tool or something) to get a list of all these unused files or/and delete them?
A manual approach - If you have Resharper installed, you can right-click and choose "Find Usages" this will look in your project for a reference to the selected image.
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
help, losing extension when use FileReference download
Hi!
I'm having an issue that looks common when using the FileReference class in FP10 when saving a file.
The whole thing works fine as long as I don't change the default filename. If I do, then I loose the extension of the file... which is annoying >_<
I haven't found any "acceptable" workaround, but the posts I've seen are from a couple of months already. So I'm inquiring hoping that something's been done regarding this issue since then =)
Regards,
BS_C3
The only thing i am aware of that you can do is: After succesfull saving check the filename and display a warning if the user used the wrong/no extension.
This question already has answers here:
How to create, structure, maintain and update data codebooks in R?
(5 answers)
Closed 5 years ago.
In analyzing data the metadata about variables is extremely important. How do you manage this information in R?
For example, is there a way to specify a label that will be printed instead of the variable name?
What facilities are there in R for this?
Quick suggestions that come to mind are
attributes to store data along with an object (as Frank Harrell has championed for a long time)
the comment() function can do parts of this
the whole gamut of object-orientation to achieve different printing behaviour etc
Use the repo package. You can assign each variable a long name, a description, a set of tags, a remote url, dependency relations and also attach to it figures or generic external files. Find the latest stable release on CRAN (install.packages("repo")) or the latest development on github. A quick overview here. Hope it helps.