pwm1234's profile - activity

Can you use CV_MAKETYPE macro as discussed here on StackOverflow?

I do not have first hand experience doing this, but I believe you should be able to do this with a custom datatype where the depth matches your data layout.

Steven, you say you understand why they changed it. I do not. In fact, a little earlier today, I asked this question looking for some insight as to why they changed it. My experience has been doxygen is great for API reference documentation. But it is not as good at the often more important documentation like tutorials and user manuals. OpenCV 2 with its sphinx documentation had already gone to the trouble of using sphinx, so I was surprised (and disappointed) to see they abandoned it for doxygen. I think using doxylink and/or breathe to combine doxygen with sphinx would have been better.

Why did the OpenCV team decide to change its documentation tool from sphinx to doxygen? I like the sphinx generated documentation and thought OpenCV 2 had both nice online and printed documentation that was relatively easy to author. I have searched but have not seen a discussion of why change to doxygen.

I asked this same question on StackOverflow, but it was closed as being off-topic. I am hoping to get some insight from this forum.

Thanks!