Saving settings on the server

[manybodycpa]

After, for example, enabling autosave and setting the framerate for playback, the settings go back to the default values after the task is closed and reopened. Is this the expected behaviour?

[bsekachev]

@manybodycpa
It is expected, but we can consider the issue as a feature request

[manybodycpa]

Thanks for the reply. I would like to kindly request an option to remember the task settings if others find that feature useful.

[manybodycpa]

Alternatively, is there a way to just change the default settings for all tasks for a given user?

[bsekachev]

Related with #747

[bsekachev]

@manybodycpa

No way except of changing source code.

[cpudney]

Yes, this would be a useful enhancement. We have to enable autosave for each annotation job whereas we'd like this setting persisted indefinately.

There are other preferences we'd like persisted too, e.g. how annotations are coloured (I prefer by label) and opacity. Should I put this in a separate issue?

Thanks for a great tool.

[johanneszellinger]

Hi everybody, we stumbled across this issue since we have the same problem, that we want to set and retrieve the user settings (especially autosave) on the REST server.

In our case registering users, setting up annotation jobs and so on is done automatically by our own server which talks to CVAT's REST Server, the actual users should only work on the annotation itself. After registering a new user we would also like to turn on the automatic saving feature for each user, which is not possible, if these settings are only stored on the client.

I'm not quite sure how #3017 solves this particular issue, but we might be missing something here that would solve our problem.