👍

@terfendail is there a way to expose the enums to the python interface? If so, that would make it much easier to create these interfaces. To my knowledge, the only reason the function createStitcher exists is because python has no knowledge of the underlying enums

Hi,

it is possible and quite easy see https://github.com/opencv/opencv/blob/master/modules/stitching/misc/python/pyopencv_stitching.hpp

I agree with you that it would be much better to export the enum and create function, rather than creating yet another auxiliary function to create a Stitcher. There are already too many ways to create a Stitcher, it is a mess. I hope it will be cleaned in OpenCV 4.0.

Sorry for being late, but you were quite fast with merging this. I think we can still remove the new function, since there has been no release, right?

@hrnr Thanks for explaining.

I've used SWIG before to export my C++ interfaces to Python and never actually created templates myself. Thanks for showing me the example.

I personally think the old function should be removed too, I just couldn't find an example quickly. I'll try to implement the change, compile and update the PR.

As far as I know OpenCV uses custom build binding generator and not SWIG. You can find it in the python module if you are interested.

Hi @hrnr

I added

typedef Stitcher::Mode Mode;

template<>
PyObject* pyopencv_from(const Mode& value)
{
    return PyInt_FromLong(value);
}

but now I get

12>C:\Users\mark\git\opencv\modules\python\src2\cv2.cpp(1855): error C2129: static function 'bool pyopencv_to<Mode>(PyObject *,T &,const char *)' declared but not defined
12>        with
12>        [
12>            T=Mode
12>        ]

Is there an easy way to generate that function without having to manually add the keys to a string compare dictionary?

I'm not an expert in OpenCV python bindings, maybe @alalek knows how to do this properly?

@hmaarrfk Could you please check the change with latest master?
I've tried it and it compile fine at least for my configuration. Also it looks like it would be enough to have only
typedef Stitcher::Mode Mode;

However at the moment such typedefs are added to cv2 namespace so it could became cluttered quickly.