Home → Beta Testing →

keyboard layer - iOS MMD Composer 1.0 (47)

• Edit

vwc

27 May, 2018 10:42 AM

Thank you for adding some functions for the keyboard button bars

Generally I suggest that at least you should add

1. a tab key. This is essential for the use to add rows in a table. At least for me the easy adding of table rows is one of the distinguishing features of MMD Composer.
   
2. cursor arrow keys.

iPad

The keyboard button bar works differently whether the keyboard language includes a predictive language or not.

If it has a predictive language then the buttons are pushed to the right hand side, if not then they take up the whole row.

For the iPhone the predictive language bar and the keyboard button bar are always separate in MMD Composer.

Screen shots attached.

• iphone_-_predictive_language_bar.jpg 259 KB
• iPad_-_predictive_language_bar.jpg 256 KB
• iPad_-_Non-predictive_language_bar.jpg 250 KB

1. Support Staff 1 Posted by Fletcher on 27 May, 2018 02:42 PM

   

   1. I'll think about tab key vs another way of handling tables. I would really like to minimize the number of buttons as much as possible. And I would prefer to try and find the "right" set rather than just leave it to the user. But ultimately that might have to happen.

   2. cursor keys -- Are these necessary since the keyboard itself allows you to move the cursor (either with "force touch" on iPhone or two finger touch on iPad, at least for me with iOS 10 iPhone and iOS 11 iPad)? Achieving the same functionality (or even more) with 0 buttons seems better than using 4 buttons. (I could consider adding a shiftUp/shiftDown pair to go along with the indent/outdent to allow you to move selected text up or down in the document, but that is slightly different.)

   Yes -- iPhone and iPad work differently.

   • Edit