I've just started using TV Remote and one of the first thing I noticed is that it acts (sends IR) when the button is released - not when it is depressed. Thus it doesn't feel as responsive as it could have if it reacted on a depress. What do you think? I guess this is due to the application itself and not WinCE?

That's the standard way buttons act in ALL versions of Windows.

Ahh... that's true. But still everything is possible to implement I guess. And I think it would have been better if it not acted this way. But it's only a small nuisance though...

Btw how is the real thing working? (Pronto)

sends the signal when the button is pressed

I mailed this to PDAWin several times. The more important thing is that this is the reason why screen buttons cannot repeat in TVRemote.
I think it HAS to be fixed, and I know, it's not that difficult. It simply doesn't seem to bother them.
The repeat on the hardware button also isn't correct, because they simply repeat the complete code instead of reproducing what the original (learned) remote does.
Perhaps some more complaints would convince them to put it on their ToDo-list.

Wilhelm

I have already sent them an email about this. Haven't got any reply yet though. I'll let you know when(if) I do.

Button repeation is also something I really miss and it would have been fairly complete for my usage if these things where solved. Too bad...

Maybe all people reading this should give them a nicely written suggestion to implement these things?

But it seems it can be done the other way, because Nevo sends IR as soon as the button is pressed and stops sending when the button is released -- just like a remote control should.

Total Remote sends a command the moment you hit the button, and if you hold the button it keeps sending the command. As alfaman said, just like a remote control should.

[Link: griffintechnology.com]

Don, have you given any thought to OEM-ing the code for your IR Emitter to the people at PDAWin?

@Don
The only problem is, that Total Remote doesn't learn the codes correctly, so that they could be repeated. E.g. my Yamaha AX1 doesn't work, my Toshiba TV works insufficient. It's even worse than PDAWin.

Wilhelm

This message was edited by Wilhelm on 12/20/02 14:54.34.

westmetro:

I had exactly the same thought tonight. They really should share their efforts. We would have the best of both worlds: a nice software with CCF support AND an IR emitter that works with most PocketPCs instead of a subset of iPAQs...

Hope they consider this idea seriously. The potential for both companies is immense. Together they could take on the Philips Pronto using inexpensive devices such as the new Dell Axim X5.