[Windows Mobile Apps and Games] mike2nl:
Hi rcolonel,

thanks for all your answers and your kind words about my review. I think this is normal, because you have spent so many time for that. I think this is the minimum what you can expect from users. I'm also a coder and sometimes i wish i had some detail reports. I hope you have spent not so much time to think about my questions :D.

-->Probably, the overview of several channels is not rationaly

What i mean was, it is possible to select a channel. Not all 4. This comes via browser. Forget this please. But a chance to select the right channel that will be nice.

-->G-sensor? Which function for G-sensor for an application should be given?

I was thinking to use g-sensor for the PTZ control - left, right, op and down. Not more, because then it is over with the g-sensor. There is an easy api for that, but we will see.

-->First, the conception of RC Camera is next:

-->1. It must be a "light" app - must work satisfactory with the old, slow devices (like my HTC Touch).

Yes, you are the first one, so far as i can see, who tkaes care about that. Take care for older phones. Very good idea...

-->2. The app must consume low level of a traffic - because it suppose to monitoring camera through Internet.

Thats right, but it is possible todo that? I ask because the most of us using wifi (free accesss points (mc donald, ...) or at home or on the work). Possible there will be a chance to do that for one of the next versions.

-->3. The app must be suitable for any ip-cameras. Acoording to the first point, to add a skin supporting is not rationaly. Also, a skin makes a visible area of picture smaller.

Also right, i had ask because it will be a little gimmik to chance the background. This will be funny.

-->As of the second one, RC Camera uses jpeg-mode of ip-cameras to reduce the traffic.

Yes right, i know this, because i write some parts in operating systems for hardware like that ;).

-->Hereupon, it is not possible to use a steaming data of a camera - the short refresh rate (like a video) and sound supporting.

There is no need for streaming and sound. It was an idea because the axis have support for things like that over many years. What i mean is a refresh rate smaller then one second. The idea goes to 500ms, 1sec., 2sec, 4 sec., 8sec, and so on.

-->But, in practice 5-20 seconds of refreshing are enough to control a remote situation.

Normally i wil say right, but not in all cases. So when your app have the possibillity to change to 500ms it is more then enough. There will be NO garantie for the right function. The most cams (~60%) can't do that. But the newer hardware well. I have tested here moer then 20 different cams for an hospital security application. And the guys have now seen your app on my dusk-phone. You can imagine now what's going on here?

-->As of the third reason, I can't add a remote setup control, becouse it is a unique function for a certain camera.

Oh have i asked that? Please forget it. No need. Sometime i'm so enthusiast about things. And your app is one of them.;)

-->In next release (version) your remark about the mistakes in finger PTZ control in non fullscreen mode will be taken into account. Also, it is a really good cc.torres's idea - to add a digital zoom function.

Thanks a lot for this solution. I will be wait for that and i will do my tests again.

-->About the payment: I am not a proffesional programmer, it is just my hobby ... and the first experience of working out the application for mobile device. ;)

But there are now people who have seen your app on my phone. There is a small world of people who will have things like that. I think we have to PM for that.

Thanks for your time, rccolonel