Problem with myKbd

[ziggy]

I installed myKdb yesterday to have a look at it. Everyhing worked fine, using the ATOMIK keyboard. When I switched on my TX this morning, it asked for a password (as normal). Unfortunately, I was unable to enter anything at all using the ATOMIK keyboard. Also I could not change from keyboard to graffity, nor could I switch on the write anywhere feature. Hard reset and restore from backup (NVBackup) did not work, still gave the same problem (not a surprise since the backup was made in the night and still contained the myKbd application). I was able to restore after hard reset followed by a hotsync. Any ideas what went wrong?

[ziggy]

I just realised that I did not add myKbd to UnCache. Could that have caused the problem?

[cyberdude]

That would certainly explain some of your problems. Although I've never tried it I would think you would be able to use grafitti.

[FerdFerd]

I use mySkin, not myKbd, but it must be in the UnCache list for it to work correctly. I would assume the same to be true of myKbd.

[ziggy]

Thanks for your input. It seems that it was indeed forgetting to include myKbd in Unchache that triggered the problem. Initially it worked fine, but in the night an automated backup was done, which was followed by a soft reset. Because of the latter myKdb was not notified properly; the keyboard still showed up, but was not responsive anymore.