Pinning of non-default fields

[quincylvania]

With #5582 we can now define additional per-preset fields so users can add all sorts of detailed information to features from the "Add field:" dropdown without cluttering up the default sidebar. However, there are times where users may want to use one of these extra fields very often and repeatedly using the dropdown would be cumbersome.

We should let users manually "pin" fields so that they show up by default.

See #5733 for a better UI when there are more than three buttons.

One possible UI:

[bhousel]

However, there are times where users may want to use one of these extra fields very often and repeatedly using the dropdown would be cumbersome.

Could we just have a field be "pinned" after the user uses it once?
I'm mostly trying to think of ways to avoid adding a new feature that we might not need.

[slhh]

Could we just have a field be "pinned" after the user uses it once?

This could essentially work, but II see the folllowing disadvantages:

• The user can't select a fully tagged example feature and just pin the fields which are shown due to tag presence.
• The all fields section could become very long, especially if the pinning is not stricty preset specific.