Undo/Redo in Software Licenses > license key

DavidB

The "Known Issues in 1Password 4 for Mac" announcement says, "Undo/Redo is not yet possible in the note fields and also the Secure Note items." Undo/Redo is also not possible in the license key field in Software Licenses.

Thank you,

David

sjk

Thanks for reporting this, @DavidB. I've noted it in the bug report we already have open. The general issue is that Undo/Redo isn't currently supported in multi-line text fields, but is planned to be fixed in a future free update.

DavidB

I am curious to know how this kind of bug is missed in a beta group of 20,000 participants? (Not a rhetorical question--I really want to understand how the process works.)

Stephen_C

@DavidB, I can't speak for AgileBits but have been part of the 1P4 beta process for a while. In fairness to AgileBits I don't think the bug was "missed" in the beta process. In fact, I know it was identified. I suspect that, with a re-write of 1P from the ground up, and something of a deadline, it's just something that there wasn't time to fix. The beta testing was intensive and generated much activity on the beta forum. No doubt AgileBits had to prioritise what happened before release and what was left for version 4 updates afterwards.

I do emphasise I'm not speaking for AgileBits but merely as a beta tester. If either you or they think I'm speaking out of turn, please forgive me for doing so!

Stephen

MikeT

Hi @DavidB,

Everything @Stephen_C mentioned is correct. As you noticed, it's already on the Known Issues.

We'll be releasing a lot of updates to include improvements to eliminate most of the Known Issues and add more new features as well. We work in an iterative development process, which means we don't include all the features at once in a single big version like a Snow Leopard release with 300+ features. That'd mean 1Password 4 would be released in 2020 instead of now where majority of folks can enjoy most of the implemented features.

Not only that, such a release can be difficult to debug and support. We start small, improve through iterations with suggestions from our customers and then add more big features over time. If you look at our 1Password 3 development, you can get an idea of what 1Password 4's development is going to be like over the next few years.

The bug you reported is not high on our list to fix in the first release (in other ways, it is something we can fix down the line and not hold up the main release) but it will be fixed in one of the smaller updates to come.

Stay tuned, we'll get this fixed for you.