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
Is your feature request related to a problem? Please describe.
I have a document annotation campaign, and my annotators are only using the key bindings to annotate faster. They are complaining because when they want to validate their annotation, they have to use their mouse to dismiss the warning pop-up. This is a time loss and disrupts their workflow.
Describe the solution you'd like
I would like a toggleable button in the workload admin panel, under the dynamic assignments option, to disable or enable the warning pop-up.
Describe alternatives you've considered
A key binding that dismisses/confirms the pop-up would also work.
Additional context
No additional context.
The text was updated successfully, but these errors were encountered:
reckart
changed the title
Disable warnings when validating annotation on dynamic workload mode
Option to disable the finish confirmation dialog in dynamic workload mode
May 30, 2024
Looks like we already have an option to disable the confirmation dialog. It should be accessible from the settings dialog on the dynamic workload page. Does that meet your needs?
Is your feature request related to a problem? Please describe.
I have a document annotation campaign, and my annotators are only using the key bindings to annotate faster. They are complaining because when they want to validate their annotation, they have to use their mouse to dismiss the warning pop-up. This is a time loss and disrupts their workflow.
Describe the solution you'd like
I would like a toggleable button in the workload admin panel, under the dynamic assignments option, to disable or enable the warning pop-up.
Describe alternatives you've considered
A key binding that dismisses/confirms the pop-up would also work.
Additional context
No additional context.
The text was updated successfully, but these errors were encountered: