update lib to new c++ interfae about cvblob

[GoogleCodeExporter]

Are you sure that Mat type does not work with cvBlob? Which functions have 
problems?

Anyway, I will research that.

Thanks!

Original comment by [email protected] on 7 Mar 2011 at 6:14

• Added labels: OpSys-All, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yes, type Mat from OpenCv2+ seems to be not supported by the latest stable 
release of CvBlob.
Right now i have this problems:

cannot convert ‘cv::Mat’ to ‘const CvArr*’ for argument ‘1’ to 
‘CvSize cvGetSize(const CvArr*)’
cannot convert ‘cv::Mat’ to ‘const IplImage*’ for argument ‘1’ to 
‘unsigned int cvb::cvLabel(const IplImage*, IplImage*, cvb::CvBlobs&)

Original comment by [email protected] on 24 Apr 2011 at 3:44

[GoogleCodeExporter]

Hi,

Soon I will release a new version of cvBlob, after that I will try to refactor 
the lib to support the new OpenCV C++ interface, changing the cvBlob interface 
as well.

Suggestions and any kind of help will be welcome!

Original comment by [email protected] on 28 Apr 2011 at 7:15

• Changed state: Accepted

[GoogleCodeExporter]

Actually, to me it's working quite fine with OpenCV2.2. Just explicitly create 
a IplImage header for your cv::Mat and you're good to go. The overhead of that 
operation is marginal.

But indeed, it would be nicer to have the real deal as interface...

Example:
//m_map is a cv::Mat, single channel.

IplImage ipl_map=m_map;

IplImage *labelImg=cvCreateImage(cvSize(ipl_map.width,ipl_map.height), 
IPL_DEPTH_LABEL, 1);

cvb::CvBlobs blobs;
cvb::cvLabel(&ipl_map,labelImg,blobs);

Original comment by [email protected] on 1 Jun 2011 at 2:25

[GoogleCodeExporter]

Issue 36 has been merged into this issue.

Original comment by [email protected] on 24 Jan 2013 at 9:00