You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature request to improve UX is related to this issue: #26 .
Issue: When tagging (or removing tags) from a lot of items, once the user initiates the action, there's no feedback that anything is happening. It would be reasonable for a user to assume that everything happens almost instantly, even though this isn't true.
Solution: Have a little notification message that says the tagging is happening. If you want to use the same message for both adding and removing, it would be something like "Tags being updated. For hundreds of tags this may take awhile. Please wait . . ."
Then, as already happens, the "Success" notification would trigger on completion, making it clear the updating was finished.
A more front-and-center option would be having a progress bar, like the "Find Available PDFs" option currently does. I'm not sure that's worth the effort, although it would make the process more transparent.
The text was updated successfully, but these errors were encountered:
This feature request to improve UX is related to this issue: #26 .
Issue: When tagging (or removing tags) from a lot of items, once the user initiates the action, there's no feedback that anything is happening. It would be reasonable for a user to assume that everything happens almost instantly, even though this isn't true.
Solution: Have a little notification message that says the tagging is happening. If you want to use the same message for both adding and removing, it would be something like "Tags being updated. For hundreds of tags this may take awhile. Please wait . . ."
Then, as already happens, the "Success" notification would trigger on completion, making it clear the updating was finished.
A more front-and-center option would be having a progress bar, like the "Find Available PDFs" option currently does. I'm not sure that's worth the effort, although it would make the process more transparent.
The text was updated successfully, but these errors were encountered: