Mat_<> typedefs (Feature #2)
Description
As far as I can see, there are no typedefs abbreviating Mat_<float>, Mat_<uchar> etc.
Wouldn't it make sense to add some of these similar to the ones for Size, Point, Rect, Vec etc?
e.g.
typedef Mat_<float> Mat1f;
typedef Mat_<double> Mat1d;
typedef Mat_<uchar> Mat1b;
typedef Mat_<Vec3f> Mat3f;
typedef Mat_<Vec3d> Mat3f;
typedef Mat_<Vec3b> Mat3b;
...
Associated revisions
Patch from Kertesz Csaba:
#1: It solves a value range problem by such a v4l2 image properties which have
too narrow value range: e.g. 0-7
#2: General bug in my last patch. v4l (VIDIOCGPICT) gives back the default
image properties and changes the webcam to the default state. There is no
feedback from v4l if user modifies the image properties of a device. The
functionality after these modification is normal: OpenCV returns with the
default or last adjusted value of an image property.
git-svn-id: file://localhost/home/tolik/svnrepo/trunk/opencv@451 c5418bc3-7546-4aae-8bad-fa6f2f3e53e6
Patch from Kertesz Csaba:
#1: It solves a value range problem by such a v4l2 image properties which have
too narrow value range: e.g. 0-7
#2: General bug in my last patch. v4l (VIDIOCGPICT) gives back the default
image properties and changes the webcam to the default state. There is no
feedback from v4l if user modifies the image properties of a device. The
functionality after these modification is normal: OpenCV returns with the
default or last adjusted value of an image property.
git-svn-id: file://localhost/home/tolik/svnrepo/trunk@451 c5418bc3-7546-4aae-8bad-fa6f2f3e53e6
Small fixed #2
updating tutorial #2
Merge pull request #2 from apavlenko/ocl_mt_test
minor improvements
ipp: some functions are not available in the ICV package #2
History
Updated by Martin Baeuml about 15 years ago
Added in SVN r2615.
- Status changed from Open to Done
- (deleted custom field) set to fixed