Benny wrote:Another thing (and maybe the most important) is that if you add something like this, then most of the false reports will be excluded.
Since it will not be enough to just hit one of the buttons by a mistake.
Or if you think you have another program running up front, and hit some buttons on purpose for that program while the screensaver are running.
Quote:
I'm not sure I understand what you mean... If you press by mistake the "*" button and there is nothing, just press the same button again in order to release the GPS. Nothing is sent in this case.
I have a multitask phone and a lot of the programs have shortcuts, like Maps when you are on a route the 1 button switch between 2D and 3D, nr 2 button store your location and 0 show your position.
A lot other programs have the same, I dont use the keyboard lock when I am out driving and if I think I know what program are running up front I just push the correct shortcut 2 times, the first one to shut of the screensaver and the second to select the wanted command.
If I then don't have the expected program up front, but FoxyTag instead it will mean trouble.
And the other day I managed to push the nr 2 button just by a fault when I wanted to pick up my phone.
All this would had been avoided if you had added a confirmation function.
And only at the expense of 1 extra button push, the few times you actually shall report anything.