There doesn't seem to be a way to select an entire date in a "date formatted" field
I can only select individual parts of the date (year or month or date) for a field that is in "date format". It's not obvious how to select the entire date ... also, when a field is originally text, then converted to date, the conversion is weird ... there is no attempt to coerce the text into a proper date. Oddly enough, conversion from date to text is OK.
1Password Version: 5.4 beta 38
Extension Version: 4.4.4.1
OS Version: OS X 10.10.5
Sync Type: iCloud
Referrer: forum-search:can't copy a date in 1Password
Comments
-
Hello @mikejt,
We use the standard OS X date object at least for the full date and I suspect we use something similar for the month/year ones too. So the behaviour you're reporting about only being able to select individual parts is how they work. You should be able to observe the same behaviour in OS X's Calendar application for example.
We are aware of the second issue though. Another user reported the same thing a couple of months back and of course I was able to easily reproduce. Going from the Date type to Text is easy because serialising a date object is nothing more than turning 3 numbers into a string - very simple with no chance of error. Going the other way is more prone to errors as we have to assume an unknown piece of text. At the moment we avoid making a mistake by not converting at all. I agree that a user would expect it to convert though.
ref: OPM-3056
0 -
You may use the standard OS X date object, but so does BusyCal, and it's behavior is different, so they must use a different UI. In their case, a click on a date selects the whole date, and a second click selects the part of the date (m/d/y). This seems like a whole lot more "friendly" approach.
0 -
Hi @mikejt,
After looking into this a bit, I'm not entirely sure BusyCal is using the standard OS X date object, as (based on your description) it seems to behave differently than other apps that are using it, such as Contacts, Calendar and Fantastical. However, I'm no expert on BusyCal (or the standard OS X date object, for that matter), so it's possible I'm mistaken. If you don't mind, can you explain how you know (or why you believe) BusyCal uses that object?
0 -
I don't know for certain, they may implement their own, but I would think they just override the default behavior in certain cases
0 -
Thanks @mikejt! As I mentioned, I'm definitely not an expert on BusyCal, but from your description, it doesn't sound like they're using the standard OS X date object (if they were, it should work the same way as in 1Password, Contacts, Calendar, and so on).
However, the point of all this is that you prefer the way date fields work in BusyCal, and sounds like you'd like them to work that way in 1Password too. We absolutely appreciate your feedback on that! As we're currently using the standard OS X date object, we'd need to make significant changes in order for 1Password to start working differently with date fields. That's not to say we'll never do that, and I can let our developers know you'd like that, but I can't make any promises for when or if that will happen.
Thank you for taking the time to contact us about that! If you need anything else, please don't hesitate to let us know. :)
0
