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
Hi,
If you can jump to pair by its id it could be a useful feature when you have to visit several pairs (for example to discuss details with somebody).
Right now it may take some time to scroll and find pair among several thousands of samples.
In our case, we tried to review pairs with different labels from different reviewers and this feature may definitely make the experience with CAT even better.
The text was updated successfully, but these errors were encountered:
Please try: click on select, type the number, click on it. Like that don't need to scroll and can jump to specific file pair. Does it work for you? Or I didn't understand the issue correctly?
No, it doesn't work.
The issue in other words - navigate to specific file without scrolling kilometers (in case of 1000s pairs).
The way you explained could be very good.
Ah! We have ( in the front of the number. That's why it doesn't work. Thanks! Then we need to find another solution. Maybe something like this: https://select2.org/searching ?
Hi @smacker Thank you so much for the input :) We're gathering feedback from ML Team, and issues like this will be addressed after research analysis, nonetheless, thank you for your suggestion!
EgorBu
changed the title
GOTO specific file
[Feature request] GOTO specific file
Mar 9, 2018
dpordomingo
changed the title
[Feature request] GOTO specific file
GOTO specific file
Mar 9, 2018
Hi,
If you can jump to pair by its id it could be a useful feature when you have to visit several pairs (for example to discuss details with somebody).
Right now it may take some time to scroll and find pair among several thousands of samples.
In our case, we tried to review pairs with different labels from different reviewers and this feature may definitely make the experience with CAT even better.
The text was updated successfully, but these errors were encountered: