Change default settings: 1) auto_save: false -> true; 2) store_data: true -> false

[wkentaro]

I've noticed myself (almost) always use labelme --nodata --autosave IMAGE.jpg when I annotate.

• "saving imageData" has a drawback of inefficient image storing by base64
• "no autosave" has a drawback of new user expectation on GUI app (as autosave is more common these days e.g., MS Powerpoint)

Changing the default has friction for existing users who expect the existing behavior, but I think it's worth it.

To keep the original behavior, power users can always use: labelme --config '{"store_data": true, "auto_save": false}'

Since this is a breaking change, I think we should bump the major version: v5.x.y -> v6.0.0

[wkentaro]

/cc @RoyiAvital

[RoyiAvital]

Wouldn't people who already has the current default in their labelme.rc will keep their settings on upgrade?

[wkentaro]

yes, but the existing users would expect the existing behavior when they fresh-install labelme on their new machines.

[RoyiAvital]

They may. But why is that breaking?
If you move an option from one menu to other, is that breaking?

I think anything which is preference based is by definition non breaking.

What I think is a bug is that the menu does not show the activated option well enough.

[wkentaro]

Because if you use labelme in a scripting, changing the default behavior causes the pipeline break (e.g., imageData is missing).

auto_save can probably be changed without breaking.

[wkentaro]

What I think is a bug is that the menu does not show the activate option well enough.

Yes, I've noticed that just recently (seems it's Windows specific). Fixed by #1657