Open GoogleCodeExporter opened 8 years ago
Yes, I changed the behavior of the date row.
I will add a preference to use the open behaviour into the button screen in the
next version. Sorry for the hassle
Original comment by roflharr...@gmail.com
on 6 Aug 2012 at 5:55
Thanks, that'd be great! I have a toolbar with a button whose action is Add,
and I use that to create events, so I don't need a secondary way of doing it...
but I do really benefit from a quick way to get to a view in Calendar, which is
what I use date rows for.
Original comment by m...@melez.com
on 6 Aug 2012 at 6:45
No problem. You might notice that the date row "add" should actually set the
date for you. Also, most calendar applications don't support the deeplinking
function.
Original comment by roflharr...@gmail.com
on 6 Aug 2012 at 6:48
Yes, I noticed that. But typically I'm adding it to the near future (often to
today), and it's easier to tap the Add button and then adjust the date slightly
(if at all) in the Create Event form.
That's true for events in the distant future, too, since scrolling through the
widget to find a date is cumbersome, and the widget only goes so far anyway.
For example, today I added a concert I'm going to see at the end of October,
which I can't do by tapping a date row, as the widget doesn't look that far
ahead.
Note also that the Add button is always in the same place, so no matter when
the event occurs, I always tap the same location on the screen of my phone to
add it. There's nothing like consistency to make it possible for muscle memory
to smooth an interaction!
Original comment by m...@melez.com
on 6 Aug 2012 at 7:04
Original issue reported on code.google.com by
m...@melez.com
on 6 Aug 2012 at 5:51