-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved interface of interactors on UI #2054
Conversation
Pull Request Test Coverage Report for Build 7214
💛 - Coveralls |
The PR is ready to review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It had the same behaviour with export Configuration.
Fixed
Hmm. Cannot reproduce. I will try more, but try to restart server, may be it will help. |
I suppose it was related with label selector (wrong onChange function as I later found). Should be fixed for now. |
const result = await core.lambda.call(jobInstance.task, interactor, { | ||
task: jobInstance.task, | ||
frame, | ||
points: convertShapesForInteractor((e as CustomEvent).detail.shapes), | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As i understand, negative points in this patch works like positive, isn't it? Maybe it's better add a filter for its or something else, what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, yes.
Need to update server API for interactors (an interactor on the server should itself decide what to do with negative points)
We can filter these points for DEXTR only on UI (till the next PR), but what problem we are trying to solve?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a little bit confusing that negative points works like positive. Maybe it's better to temporary disable ability to create negative points in UI, since we have no interactors to work with and in the next PR with extended interactors functionality enable it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And in the next PR when we enable them, they will be confusing again.. Or maybe user will input some negative points in the future and they are ignored, what also can be confusing for him, or a user inputs four points (two are accidentaly negative), they are filtered and dextr gets two points instead of 4. Here are a lot of open questions. If it makes you worried, we can discuss it tomorrow on the meeting
@bsekachev , it is a great feature! It works like a charm. Please give me a day to experiment with it. Thanks! |
When I press ESC, the drawn polygon isn't removed. Is it expected? |
@bsekachev , should we introduce semi-automatic hint in addition to MANUAL and AUTOMATIC? What is your opinion? |
@bsekachev , should we allow to move to another frame during interaction? For now CVAT doesn't and it is good from my point of view. The reason of the question is because for another drawing methods we allow. Should it be unified? |
No, It is expected that drawing will canceled. |
If we get a request for that, we can. But right now I would suggest left it as is. |
Historically we didn't strict moving between frames during drawing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Motivation and context
How has this been tested?
Manual testing
Checklist
develop
branchcvat-core, cvat-data and cvat-ui)
License
Feel free to contact the maintainers if that's a concern.
Checklist: