Hmm... as mentioned below, I haven't tested with a keyboard and I guess I didn't properly consider that use case. I found the calendar control easier to use than the on-screen keyboard, but can see that a plugged in keyboard may shift that balance back the other way (hence why we have always allowed typing dates on the Desktop version). Where would be the best place to add it in your opinion? One option could be a *press + hold* in the Start or End date at the top of the widget could make it directly editable, whereas the tap would retain its current behaviour. Matt
Ideally it would simply detect keyboard input once focused and allow typing without any messing about.
Just checked how it works on desktop - the workflow for adding an event with an external keyboard should be pretty much the same on both iPad and Mac. As far as possible the iOS app should support the same keyboard shortcuts as desktop - that's one of the genius things about Ulysses, it's increasingly the same basic interface on desktop and iOS.
Since this is a use case that obviously isn't one you personally have, maybe I should explain it. I want to be able to do pretty much all my writing and time lining on my iPad. I don't mind having to go back to my laptop to finalise documents or whatever, but I spend enough time at my desk with my work computer as it is, so I need to be able to take my iPad down to the shed or coffee shop or travelling and to work on documents, add to timelines as I do research and share at least a basic PDF/CSV with people when I'm doing that. I spent three weeks in Greece with "just" an iPad Pro 10.5" with the keyboard cover (such hardship, I know) typing timeline notes into Ulysses so I could sync them up when I got back. I'd much rather use the same set-up almost all the time I'm doing study/writing work: I'd hope that the iPad would be the primary machine I'd use Aeon on.
Hi, Thanks for the additional context around your work. I snuck out and bought an iPad keyboard today so I could start using it with the keyboard, so I will take a few days to acclimatise myself to the keyboard use before I work out exactly how to handle it. I agree that adding a few keyboard shortcuts would make sense. To clarify your suggestion, I believe you are asking for something like the following *if a keyboard is connected*: - Tap the row showing the full date (e.g. the "Start" or "End" row for events), and this would both have the current behaviour of choosing which date is affected by the calendar widget below, but would also become immediately editable if a keyboard was attached; - I gather that it would be fine to leave the display and behaviour of the rest of the calendar those fields below as-is, so the user can choose to use either input method? - Thirdly, any text typed into the date field by the user would update the calendar underneath accordingly so that it showed the same date. That sounds plausible, but I will play around with the keyboard for a couple of days to give it some thought. I assume Apple make it possible for developers to check if a keyboard is attached, but I will need to do a little bit of research to confirm that.
I agree with Colman - it would be much easier for keyboard users to be able to tap out dates rather than scroll through the months & years. Using the calendar selection system as it is now is a PITA for me, too. I use a Zagg keyboard with my iPad Mini, by the way.
Hi Julie, Thanks for the feedback. It certainly makes sense for keyboard users. Just to make sure you are getting full efficiency from the current setup: - You can tap on the year or month to get a table version to select a year or month quickly, rather than scrolling through with the left/right arrows. - Those tables are left/right swipeable, if you want to get to a year range nearby... E.g. If it is showing 2001-2020, swipe to see 1981-2000 etc. - Finally, you can press and hold the year name to make it directly editable, if you need to jump very far away. See the Calendar Picker list here: http://aeontimeline.helpscoutdocs.com/article/33-gestures-and-interactions None of which is to say that for keyboard users there isn't a better option, but we tried to design a UI that would function with the least taps for touch users, so hopefully some of that will make it alittle smoother/easier for you in the mean time. Apologies if you are across this already.