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
Problem Statement
If the user wants to clear all the previous alignments or half aligned words, they have to manually move every aligned word which is cumbersome.
Proposed Solution
Provide a button to clear the alignments that should send all the words to sent back to the word bank allowing the user to start over fresh.
Details
On clicking the Clear alignment button, there should be a prompt for the user to confirm if they want to claer the alignments. This is necessary to avoid accidental clicks. If user selects Yes> this should send all the words to sent back to the word bank; If No then the words/alignment should stay as is.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Looks good in v2.1.0 build f845565 QA. Clear/Reset button is available in Alignment screen and it works as expected. When clicked, a prompt is shown which confirms if the user wants to clear alignments. On selecting Yes, all words are sent bank to word bank and when Cancel is selected after that, no alignment is lost.
Problem Statement
If the user wants to clear all the previous alignments or half aligned words, they have to manually move every aligned word which is cumbersome.
Proposed Solution
Provide a button to clear the alignments that should send all the words to sent back to the word bank allowing the user to start over fresh.
Details
On clicking the Clear alignment button, there should be a prompt for the user to confirm if they want to claer the alignments. This is necessary to avoid accidental clicks. If user selects Yes> this should send all the words to sent back to the word bank; If No then the words/alignment should stay as is.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: