Couple other related problems with iPhone keyboard: 1. If the code repositions the textarea to fit right above the keyboard (so user can have some contiguous text above), the keyboard loses track of its edit "lens" and still activates the lens in the original place (which is where it scrolled the textarea initially, half way between the top of kbd and top of screen). Laying down two fingers onto the textarea resyncs the lens again.
2. When Enter is pressed, very often the keyboard scrolls the text area from the case (1) (i.e. the area which was moved down to cover the default gap), back to the initial position with the gap. This behavior is erratic and there seems to be no pattern in their decision which 'Enter' will cause the gap to reappear. Fighting it by scrolling the area down on each such uninvited scroll (which doesn't appear as event but has to be detected from a timer event) ends up bringing up the lost lens problem described in #1, hence its not worth the trouble. Altogether, it seems Apple has rushed this keyboard "design" out the door well before it was ready for developers. Hopefully the upcoming versions will fix it up and provide a proper interface for keyboard activation, control and customization (e.g. key caps & codes produced) by the applications. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
