Guys please, this proposal on devtalk makes a lot of sense:

Confirmed. Might be related to ➞ T70095

Working fine here.

T62924

👍

The "recents" section is still there?

In rB8f55794c0e803ec5454febe2e45651c721f62c8f#245544, @noki paike (amonpaike) wrote:

a little bug,
if I change the color of the icon and save a theme, it remains saved in the theme, but when I restart blender, the folders icon turns yellow as default.
to restore the theme folders color, I have to reselect the theme.

Yes, I can confirm. It never worked, even in the sculpt branch. (Windows)

Confirmed.

In T69391#766999, @Harley Acheson (harley) wrote:

Why not change the width of the active versus inactive scrollbar? This way you can get away with a narrower gutter since it would look okay to have the active scrollbar take the entire gutter space.

@Paul Kotelevets (1D_Inc) Hey, instances moving when changing the original object's origin is an expected behavior, even in other 3d apps. https://i.imgur.com/D0oTnrX.gif
While it would be nice to have an additional option to not move the instances, this is not an issue at all.

In T69132#762132, @Benjamin Sauder (kioku) wrote:

it's not possible to snap the origin onto the object itself.

Should it be displayed more prominently in the header - instead of using a popover?

In D5577#127524, @Ludvik Koutny (rawalanche) wrote:

I don't think it's a good idea to have an enum toggle between scale and dimensions. It should just mirror the layout in the sidebar.

In T69003#761596, @Ludvik Koutny (rawalanche) wrote:

1. It needs to be decoupled from the "Pivot Point" popover
2. It should have its own 3D viewport header button,

In T69003#761437, @Campbell Barton (campbellbarton) wrote:

Committed rBacdb14d264c8b4eced645673f8ae8af1a96b1a90

LOL. Clicking on a bunch of vertices one by one at a high speed is dumb imo, I'd use circle select or something else. There are much faster selection methods for this.

Whoa, that's over complicated and hidden imo. I thought it was meant to be a function of the transform tools.

Man, you have no idea how many people will be happy with this feature. Be able to directly transform the origin is a long time dream of millions. lol

Is this functionality already in master? 🤔

@TheRedWaxPolice (TheRedWaxPolice) I agree man. (only zbrush fans would understand lol)

Thanks for clearing things out. 👍

+1 for single click

@Harley Acheson (harley) To me it looks more like a color slot property. lol

IMHO, this feature "Zoom To Mouse Position" should be enabled by default for everything.
Is there any app these days that doesn't work like that by default?

Guys, the playhead text color is still broken.
I can't change the text color of the playhead. It's not linked to anything in the themes.

Yo @Pablo Dobarro (pablodp606) isn't this that feature you already experimented with?
https://twitter.com/pablodp606/status/1146063560499318784

It died?

In T68226#744930, @William Reynish (billreynish) wrote:

This is not a bug. Material nodes are not visible in Solid mode.

Great tool.

In T67997#743667, @Flo Tasser (TheFlow) wrote:

Have you guys seen this tool? It does a lot of what I think might be good to see shipping with Blender out of the box. Going to try it out for a few days!
Youtube: Blender 2.8 PolyQuilt addon
PolyQuilt BA.org Thread by the developer

In T67997#743168, @Brecht Van Lommel (brecht) wrote:

we have a rule against it.

Confirmed. Hmm

A new mode seems totally unnecessary imo. There's nothing special about retopology to have it's very own "limited" mode. This is still mesh modeling after all.
All that is need are the tools to make things easier (cuz even the polybuild tool can act as a retopo tool already), better snapping system and new mesh display modes. And that's it, no need to complicate things.

In T67520#732705, @William Reynish (billreynish) wrote:

We should be careful of making the whole UI very complicated to allow for a corner case use-case.

In T62971#731945, @Julian Eisel (Severin) wrote:

Current state of the implementation looks like this:

In D5197#119840, @Harley Acheson (harley) wrote:

I didn't know that edit mode was an issue. So I'll aim for allowing a choice of different cursors for each of edit, paint, and sculpt. With paint and sculpt getting additional choice of "none".
Once I have that ability in the patch we can then see if we need to improve these cursors, add more, etc. I'm running out of ideas with them so it might need a fresh set of eyes on it. Especially eyes that spend a lot of time editing, painting, and sculpting.

In D5197#119834, @Harley Acheson (harley) wrote:

You might want one for painting and a different one for sculpting? Anything else?

@Harley Acheson (harley) Will you add an interface where the user will be able to choose which icon he wants to use in a specific editor? (as I'm seeing similar icons for the same purpose)

In D5080#115542, @Harley Acheson (harley) wrote:

I still have a feeling we might eventually need a small selection of different cursors to select from for painting and sculpting. Otherwise I doubt we will find a nice balance that makes everyone happy.

@Robert Gallagher (robberknyght) Sorry, but the black cursor is really bad, doesn't work at all, it looks like a bug T65694

@Erick Tukuniata (erickblender) Yes.

@gsr b3d (gsrb3d) Can something like this be also made for the icons in the toolbar?

Which brushes should support vertex colors?

Yeah. happening everywhere, like in this demo scene:

Maybe this issue should be high priority???

Can we go back to the standards now? Clearly this idea of an extra menu didn't work.

@Gavin Scott (Zoot) Couldn't agree more. 🙁

In D4854#111207, @Pablo Vazquez (pablovazquez) wrote:

This solves a number of issues:

In rB688e3fed4c255ddcfe98f08d1004dc2c0abd51ef#230794, @Brecht Van Lommel (brecht) wrote:

How is it more dangerous in Blender than another app, how do separate editors or files make a difference for that?

@Brecht Van Lommel (brecht) You can see in popular apps from adobe, cinema 4d etc, that they have separate editors for things like keymaps etc..
For example, this is photoshop:

A revert function is not popular indeed, and actually is not that useful.
What we need is an option to turn on/off preferences autosaving, and I believe most users will not want to have this enabled by default, because blender preferences is very different from most softwares out there.
In most apps out there, things like keymap settings, addons/plugins, sometimes even themes, they usually have a separate editor each, and you save those settings separately. Usually those things are not part of the main preferences, that's why they can afford to have that preferences autosaving feature, because their preferences is not that complex, which is not the case in blender.
It would be nice if we could save the quick favorites in a separate file, so we could load it everywhere. Some apps gives you a prompt when quitting if you want to save the unsaved keymap changes, blender could do the same.

@William Reynish (billreynish) And what about the playhead text color, is it linked to something else at moment as well? I can't find it.

@William Reynish (billreynish) @Jacques Lucke (JacquesLucke) It seems like this commit broke the theme text color of the vertical numbers and the playhead number text colors.
Before it used to work like this: The vertical and horizontal numbers were linked to the text color property, and the playhead text were linked to the text highlight color property.

@William Reynish (billreynish) My main concern was the vertical numbers moving to the right as well, but I can see that you also got feedback from animators and you agreed to keep it on the left. So all is fine.

The vertical scrollbars in the graph editor etc, are more useful on the left. On the right they will be too far from the "action" zone. I don't think that's a good idea.

Icon outlines would do the trick, I guess.

I like that.

Perhaps the default objects should not be inside a Collection?

Why hide the topbar by default? This makes things difficult for new users.

Great improvement!
I hope you guys don't change it. This is next level of interaction. 👍

In T57727#661048, @Campbell Barton (campbellbarton) wrote:

Discussed w/ @Brecht Van Lommel (brecht) and we agreed to do the following.

• Use a popover in the top-bar to show the redo panel (so there is a way to access it when it's hidden).

In T57727#660223, @Campbell Barton (campbellbarton) wrote:

Am not convinced

@Campbell Barton (campbellbarton) Awesome. Thanks.

So If I'm using an active tool that has a custom gizmo like the extrude tool for example, it will override the transform gizmos, right?
Then if I'm running something like the inset tool which doesn't have a custom gizmo, the transform gizmo will show up?
How's the priority of this?

Awesome! I've been waiting for this since the introduction of the selection tools. 👍

@Harley Acheson (harley) Ok, Thanks.

@Harley Acheson (harley) Are those lines themeable?

Yeah. Those changes there destroyed the all thing, We are asking them to revert some of those changes but no luck. See here: https://developer.blender.org/D4529

Alright.
I hope to see something similar for the tools in the context menus in the future, specially for the edit mode tools. 👍

This also affects the tools that are in the right click context menus?
That's the part I'm most interest in. Currently the modal tools that are on the context menus are pretty much unusable, they should be calling the active tools as well.

This seems very useful. 👍

@Brecht Van Lommel (brecht) Ok. I thought it was a bug because in 2.79 it displays correctly.

In D4529#103522, @ronan ducluzeau (zeauro) wrote:

Seriously, that are awful changes.

@Clément Foucault (fclem) @William Reynish (billreynish) Just a quick question.
Why can't blender really highlight only the components (vertex/edges/faces) of the mode selected, without mixing it, like the majority of the 3D apps out there?
Quick example:

Disable "Outline" and this will go away.

Please don't.
Maybe as an option in the preferences to satisfy the Mac users.

In D3594#101059, @Erick Tukuniata (erickblender) wrote: Please provide a build so people can test and give feedback.

In D3594#101016, @Campbell Barton (campbellbarton) wrote:

hold off on this feature until after 2.80 initial release.