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
The object's details menu should have a setting to automatically hide or unhide it for all objects, including new.
Current Behaviour
Object's details are hidden by default. We have to make one more click every time to enter some attributes.
It's inconvenient.
Possible Solution
Add a setting "always show objects details" into "settings". This setting should be enabled for new objects too.
It'll let annotate attributes quickly.
Steps to Reproduce (for bugs)
Context
Your Environment
Git hash commit (git log -1):
Docker version docker version (e.g. Docker 17.0.05):
Are you using Docker Swarm or Kubernetes?
Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container
Settings option "always show objects details" already exist. I can suggest another solution:
If the button "expand all" was pressed, all new objects are created with opened details. If the button "collapse all" was pressed, all new objects are created with closed details.
My actions before raising this issue
Expected Behaviour
The object's details menu should have a setting to automatically hide or unhide it for all objects, including new.
Current Behaviour
Object's details are hidden by default. We have to make one more click every time to enter some attributes.
It's inconvenient.
Possible Solution
Add a setting "always show objects details" into "settings". This setting should be enabled for new objects too.
It'll let annotate attributes quickly.
Steps to Reproduce (for bugs)
Context
Your Environment
git log -1
):docker version
(e.g. Docker 17.0.05):Logs from `cvat` container
Next steps
You may join our Gitter channel for community support.
The text was updated successfully, but these errors were encountered: