Ask Your Question

pwm1234's profile - activity

2018-08-28 10:25:20 -0600 received badge  Notable Question (source)
2018-01-15 14:07:51 -0600 received badge  Popular Question (source)
2016-04-22 20:59:04 -0600 received badge  Good Question (source)
2015-08-03 08:48:05 -0600 commented question Using strided external array as cv::Mat

Can you use CV_MAKETYPE macro as discussed here on StackOverflow?

2015-07-28 11:35:13 -0600 commented question Using strided external array as cv::Mat

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.

2015-07-26 18:46:23 -0600 received badge  Nice Question (source)
2015-07-24 09:41:57 -0600 commented question OpenCV 3 doxygen documentation still very counter intuitive

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.

2015-07-24 09:14:49 -0600 received badge  Student (source)
2015-07-24 08:40:39 -0600 asked a question Why did OpenCV 3 change its documentation tool from sphinx to doxygen

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.