#20 no probe flag for vfw

[Jarek Czekalski]

--no-probe flag prevents vfw from probing all formats. Instead the current format is used. Actually the probing is done, but is limited to this very format. It significantly speeds up zbarcam initialization.

I think that this should be turned upside-down and the default mode for vfw should be --no-probe. But at the moment it's a --no-probe flag.

Spadix, could you review the patch to check whether my approach is right. The biggest issue is how to pass a flag from zbarcam to vfw. I followed the way through processor and video. That's the way size forcing works. I intend to post several vfw patches. I hope I partially convinced you that this is not a waste of time.

When I post next patches they will overlap with the current one, so I think I'll finally post a combined patch.

Waiting for your answer.

[Jarek Czekalski]

[spadix]

> I think that ... the default mode for vfw should be --no-probe

Great, I would prefer to go with that then.

There will still have to be a fallback to search for a compatible format if the default is not supported, but it should be good enough to drop out when the first one is found.

IOW- VfW only advertises a single format, which is the first in the list of [current format, preferred formats, ...] that is both supported by the driver and understood by the library.

Hope that makes sense...

[Jarek Czekalski]

As it comes to probing we have 3 modes:

A. probe
B. try current, if fails, then probe
C. try current, if fails, then fail

Current zbar works in A mode. I introduced a switch to be able to take the C mode, but only for vfw. We both agree that the best default for vfw would be B.

So now, being a chief, you must make a decision: which is to be default (different for vfw?), and which are to be possible options (only for vfw?). These options would have to be added to processor api. I agree with every solution that makes startup of vfw quick. I'll make a patch according to your directions.