#154 Processor.init on back camera of Windows Surface Pro 3.

[James Hewson]

I have created a Windows Python application that uses ZBar 0.10. I have created an EXE out of the Python app and am testing it on different Windows PCs. The main function of the EXE is to scan a QR Code and display the contents of the QR Code to the user.

The EXE works correctly on my laptop which has a built-in camera. It also works correctly on my laptop with an attached USB webcam (and also on my desktop with an attaced USB webcam).

However, when I put the EXE on a Windows Surface Pro 3 (which is the target PC), it does not work correctly. The Surface Pro has two built-in cameras (front and back). The front camera works correclty, but the back camera (which is the target) does not. When I call Processor.init I get the pop-up (as expected) that asks me to choose either the front or back camera (this means ZBar can see both cameras). If I choose the front camera, everything works correctly. However, if I choose the back camera, Proccessor.init fails.

Since the back camera on the Windows Surface Pro 3 is the target for this EXE, I am dead in the water.

Please advise on how to get Processor.init to work for the back camera on the Windows Surface Pro 3.

Thank you.

[James Hewson]

It appears that I should have set "Milestone" to version_0.10 (rather than mercurial). Sorry about that.

Also, I should point out that my laptop and desktop run Windows 7 and the Surface Pro runs Windows 8.1. (However, since the front camera on the Surface Pro works correctly, the OS version may not be important.)

Thank you.

[James Hewson]

I can occasionally get the front a back cameras to work with my EXE on the Surface Pro 3. I'm not exactly sure how to reliably do it, but it has to do with opening the Camera app, switching to the desired camera and then closing the camera app and then opening my EXE.

In any case, all that turns out to be academic since both cameras are "fixed focus" and cannot reliably focus on a QR Code at a close enough range for the QR Code to be readable.

Thanks to all the folks that chimed in and helped me resolve this issue so easily (do I detect a note of sarcasm?).