What does IPLImage being deprecated mean? Is IPLImage also being
deprecated from the C++ implementation?

Will functions like LoadImage, QueryFrame, CloneImage return and use
CvMat objects instead of IPLImages? Will the CreateImage,
CreateImageHeader functions no longer exist soon? Should I stop using
these functions?

I detected this inconistency (C++ cv_bridge returns an IPLImage whereas
Python cv_bridge returns a CvMat) when I sent an image over ROS, used
the cv_bridge python implementation to get it back into opencv and got
an error when I tried to use the CloneImage function.

Currently, cv_bridge returning CvMat means that the object type of opencv
images is different if I send them over ROS or load them from disk.

Is there a wiki page which has the roadmap for the Python bindings for
opencv?


Thanks,

Advait



On Thu, Jun 10, 2010 at 10:45 PM, James Bowman <jamesb@willowgarage.com> wrote:
> It is intentional.  IplImage is deprecated.
>
> On Thu, Jun 10, 2010 at 6:00 PM, Advait Jain <advait@cc.gatech.edu> wrote:
>>
>> In the python implementation of cv_bridge the imgmsg_to_cv function
>> returns a CvMat object instead of an IplImage. This is different from the
>> documentation and the C++ implementation. Is this intentional or a bug?
>>
>> Advait
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>
>
>
> --
> J.
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>