EdgeLib 3.0 and DirectShow don't get along...

[Cardinal]

Hey guys! So I'm doing some camera based games in WindowsMobile 5. I use direct show to get access camera frames. There seems to be a problem when using direct show with Edge 3.0. You can no longer get any sort of keypad input. If I disable the camera code it works fine. Previous to this I had used GapiDraw and there was no issues there.

Any ideas?

[edge]

Hi Cardinal,

It seems like the focus of the window is lost after creating the DirectShow instance. Does it also happen when you use DirectShow to play a video file? Also, would you like to try it on a your Windows Desktop device and see if the behaviour is the same?

Maybe you can try to post a small sample of your code (preferably the code that opens a DirectShow instance in the helloworld application)?

[Cardinal]

Well the directShow code accesses the camera and is pretty specific to WM5. I tried the same code on GledPlay which uses DirectDraw and it ran fine.

I'll see if I can get some code together for you to try.

[edge]

Please let us know and we will do our best to fix this issue.

[Cardinal]

Hi just a quick update on this.

I can get EdgeLib and my camera code working together and running fairly well with the keypad input working on my MotorolaQ.

It seems that the black jack is the problem. For instance... take the Animate3D sample.. it takes a good 2 minutes to load and show stuff on screen but it works fine on other devices.

[edge]

Hi Cardinal,

Can you tell me if the Gapidraw and Gledplay samples run OK on the Blackjack?

Also, would you like to recompile your camera application for Windows Mobile 2003 and Windows Mobile 2005 and see if there are differences?