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
Recalling an entry from history will also add it back to the history again. I think in most cases, that's not needed and only clutters history with duplicates. If the implementation is not to tedious, it would be nice if this were prevented. Recalled translations could be moved to the top of the history stack, instead.
Other details
For simplicity, maybe this uniqueness could be limited to recalled entries from history, rather than checked (by iterating through history and comparing each entry) for every entry.
Acknowledgements
I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
I have written a short but informative title.
I will fill out all of the requested information in this form.
The text was updated successfully, but these errors were encountered:
Describe your suggested feature
Recalling an entry from history will also add it back to the history again. I think in most cases, that's not needed and only clutters history with duplicates. If the implementation is not to tedious, it would be nice if this were prevented. Recalled translations could be moved to the top of the history stack, instead.
Other details
For simplicity, maybe this uniqueness could be limited to recalled entries from history, rather than checked (by iterating through history and comparing each entry) for every entry.
Acknowledgements
The text was updated successfully, but these errors were encountered: