GUI glitch when updating custom icon

smallcheese
smallcheese
Community Member

When updating custom icons there are some GUI glitches which make the process a little non-intuitive.

  1. Choose Edit on one of your items
  2. Double-click the current icon (itself non-intuitive - a frosted overlay with something like "double-click to edit" would help, especially since the removal of the drag and drop feature following Documents introduction)
  3. Choose your new icon - it will be displayed in the popped up preview window you just used to select it.
  4. Choose Done. It will, for a split second, flash up into the Item View icon position before being replaced with whatever the original icon was - this is the main issue.
  5. Choose Save - the new icon will then replace the older one.

A similar, but slightly different thing occurs when deleting a custom icon.

  1. Choose Edit on on of your items.
  2. Single-click the current icon to edit it.
  3. Press backspace to delete it - here is the problem - nothing visual happens to indicate anything has happened.
  4. Choose Save and your custom icon will disappear and the original, if any, will reappear.

Hopefully you can replicate this fairly easy and eliminate the problem on a slow news day.


1Password Version: 66003
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

Comments

  • AGAlumB
    AGAlumB
    1Password Alumni

    Choose Done. It will, for a split second, flash up into the Item View icon position before being replaced with whatever the original icon was - this is the main issue.

    and

    Press backspace to delete it - here is the problem - nothing visual happens to indicate anything has happened.

    @smallcheese: Indeed, I'm sorry for the trouble. Currently you need to save the changes before the icon is displayed, but the development team is working on addressing this. Fortunately they're both symptoms of the same problem, so it's likely that fixing one will fix the other as well. Thanks for bringing this up! :)

This discussion has been closed.