In 2.79 I currently use a similar setup and it works quite well.

I agree with Campbell here, an explicit way to save preferences even with autosave is desirable.

I haven't tried it myself, but from the demo images it does seem to make a lot of sense from a user point of view.

In D4799#109916, @Campbell Barton (campbellbarton) wrote:

The way the keymap works in this patch means you can box-select and vertex-select in one action.
The vertex maybe outside the box region you draw, making this feel like a glitch

If we always auto save preferences we lose the ability to temporarily change something for the current session alone. I often use it if I don't want to permanently change something or need it just for the current file I'm working on.
Either way I don't have very strong feelings about it, most user preferences are relatively easy to undo or restore to defaults; if you want to fully reset you can easily load factory settings by erasing userpref.blend.

This seems to be a more coherent solution. The header should consistently stay at the top

I can see how this would be a useful feature, but it can also be quite destructive if an unsuspecting user creates a new collection and suddenly finds out all his selected objects were moved there.
It also raises some questions like if objects should be moved to the new collection (removed from all current ones) or should they be linked (remain in their current collections in addition to the new one)?

In T54963#661416, @Gatis Kurzemnieks (kurzemnieks) wrote:

1. Can I suggest adding 'Duplicate Linked' as Alt-D ? I think it is even more frequently used than regular Duplicate.

These are overall nice improvements. Hovering tooltips with convenient info would also be a welcome addition.

I don't make use of render layers very often but I do frequently use multiple scenes per project. I understand the reasons for removal (too prominent, clutters UI) but I can see how it will make workflow slower for those who use it.

When one is making an effort to rename things and keep a scene tidy it is a frequent action to rename both the object and the data at the same time so having both in the same dialog would definitely save quite some clicking around for two very related actions.

Not sure if this is entirely related or technically feasible, but since settings are being moved it sounds like a opportune moment to propose such changes.

These seem to improve clarity substancially.

In T61578#623163, @Andrzej Ambroz (jendrzych) wrote:

What's wrong with this?

Agree, a lot more readable. Additionally with your proposed layout we gain collection icons aligned with child objects which also looks tidier and easier to follow.

I do like this order a lot more, it seems more organized and logical.

In D4359#98906, @Pablo Vazquez (pablovazquez) wrote:

In D4359#98903, @Duarte Farrajota Ramos (duarteframos) wrote:

PS: Please always use 2.8 for screenshots as it can get confusing for users and developers.

I would happily aprove of this change. It would single handedly solve the problem by making it immediately discoverable, at the (IMHO small) expense of a little a little getting used to the new behavior.

Not sure if it can be addressed by this patch, but it seems related.
In the RGB curves node, the wrench icon menu opens sideways to the right of the button, unlike any other, which can get annoying.

In T61492#619509, @William Reynish (billreynish) wrote:

I think the numbers for collections is a weak concept to begin with. When you have nesting and unlimited numbers of them, the 1-9 numbers don’t map logically very well.

I would oppose removing the ability to set renderabilty and viewport visibility independently.
It is one of the current strengths of Blender and one of the things I really like about it.
There are several cases where you want objects visible in the viewport but not renderable. Here are a few:

This would indeed be a welcome addition to bring back. Would it also be possible for the pop up to allow renaming of object data as well?

I agree with William I believe it is just a miscommunication issue, more specifically a matter of using the correct icon and label.
As I have mentioned before, if we named it something along the lines of "Freezing" and changed the icon to a snowflake or similar (if copyright doesn't get in the way) it would solve most confusions

Just though it could also integrate to the camera view gizmos, but your solution is indeed a lot more consistent.
It also turns the viewport text into something functional, instead of static text.

A popover menu to pick currently active camera would also be very welcome.
Something akin to what we can currently do from the Scene tab of the Properties Editor.
It is currently hard to quickly browse through all cameras views in a scene.

In D4298#97343, @Harley Acheson (harley) wrote:

But if those colors are important, and specific colors are expected, then I *could* make them dynamically too.
Or I could take the specified theme color and try to make it darker or lighter. However that has some pitfalls. It would work correctly if the theme designer used a color with some latitude, like a mid-green so I could shift it into a light or dark green.

For location and rotation randomization, an option to toggle between transforming along local (object) axis or global (scene) coordinates would also be very welcome.
For scale we only need to keep the Scale Uniform option

In rB2cc69a5e2023ddc5a6a6ebed16a5d9ea3af2eaef#215829, @Clément Foucault (fclem) wrote:

This does work for all surface types.

This used to be only supported for mesh objects in pre 2.8.
Would it be possible to add transparency support for other object types, namely bezier curves as well?

My mistake then, it does look good; especially the more blurred version test, even if the do merge a little with the borders or each other.

I tend to prefer cleaner looks, but it does improve readability in some situations.

Having no active item is a idiosyncrasy I have found before in previous versions of Blender, never been an actual problem, but is curious case to tackle.
Here is a more complete laydown of all the distinct cases I could think of, hope it helps you get this right.