Page MenuHome

Improve visual distinction between Editors
Closed, InvalidPublicDESIGN


The Issue:
It's hard to see which windows each header belongs to. There's not enough visual separation between editors.

As you can see below, it's very hard to see which editor the the headers belong to:

Improve visual separation between editors, without making the borders larger

Proposed Solution:
Add small rounded corners to each editor to make the distinction clearer

Editor differentiation before:

Editor differentiation after:

Event Timeline

Part of what makes it harder to differentiate the windows has to do with the placement of the menu strips themselves. Some windows they are on top, some on the bottom. By habit, the user would normally look on top, but for some being on the bottom requires them to remember rather than just go off of instinctual/muscle memory.

Looking at it as a whole, the menu placement in that screen grab looks to be all over the place.

One way to solve this is making sure all menu strips are on top.

It feels more consistent, normal, easier to know that the window belongs to whatever menu strip is right above it. However the problem could then be that its a bit weird having the info menu above the 3d viewport menu strip.

Thus, what if the menu strips had the same ability as the T and N panel, which is to be partially transparent or have their own color scheme.

That gives us something like this. (all I did was lower opacity, so text was effected rather than just background, alternative is to have it become fully opaque with mouse over).

Now the info menu strip clearly feels different from them 3d viewport strip.

Another variation is to have it be transparent altogether, which looks something like this (rough mock ups, not polished to look as good as it could):

Something to consider in further creating separation between windows.

Rounded windows corners and headers on top by default can solve this. I'm not fan of transparent headers. They need to be clear and simple, having 3d objects under them will create visual mess. Situation with overlapping texts can occur with Object Names displayed in 3d.

@Bartosz Moniewski (monio),

Having a slight transparency in the same way as the T and N panels can be considered "clear and simple", though I think more importantly they need to be smart and visually informative above all else. The point was not to say they need to be transparent though, you might have missed that. The point was to show how having menu strips/headers create more distinction when they are in the same place at the TOP of every window. Different variations of the header show how contrast is made between the the larger all encompassing Info header and the rest of the windows below it. Speaking headers, its only a header if its on top. By default thats not the case..

Logically headers should be on top but in blender this interface item is called that way even if it is on top or bottom. Mostly they are on bottom.
I and many users prefer to have them on top in every editor. Headers are essentially menu-bars and in almost every application these are on top of window or windows if program have multiple of them.

@DataDay (DataDay) -1 for adding header transparency, increases visual noise around the header. realize this is subjective - I just don't think its really an improvement and IMHO there are better ways to tell spaces apart (including the original proposal).

@Bartosz Moniewski (monio) I think header top/bottom is out of the scope of the proposal (off topic).

+1 Rounded corners are a good idea to separate the spaces.

Another simple thing that would help distinguish headers is to increase the contrast with the header colors. Currently, having everything the same color is making the different spaces fuse together. All of the Adobe applications implement it pretty effectively (as does Modo).

I do think the rounded corners would work well to better distinguish between editors. I also agree with @Campbell Barton (campbellbarton) that transparency is not really an improvement. It can be an aesthetic improvement to some users preferences, but should not be relied upon to improve basic readability of the editors. The same goes for colors. Yes more contrast between the main areas and their headers would help distinguish them, but this still relies on the theme and is not a universal improvement.

Ideally I think we should opt for improvements that are more universal, regardless of the users theme. The rounded corners would be one of these more universal things. Even if we don't go with the rounded corners, these are the type of solutions that can add real value.

@Scott Petrovic (scottpetrovic): While I see some value in increasing the header contrast, it doesn't really solve the main issue, which is what editor does the header belong to?

Even though it's clearer in your mockup that the properties header is a header, it's not clear if it belongs to the Properties or the Outliner above. The line is subtly darker between the areas and sub-areas, but it's so subtle that it's hard to see at a glance.

@William Reynish (billrey) good point. The contrast shows that it is a header, but doesn't really associate which editor it belongs to.

I am starting another discussion on the info space. I think that is the hurdle to overcome before we can move all of the headers to the top

The rounded corners would do the job, as they did before:

But I think this would be a regression aesthetically. At least I haven't seen a mockup of rounded corners yet that managed to retain the modern look of the GUI, and there were quite a few posted on BA.

I would rather go in the direction of removing embossing on the edge of the header that touches the window's content, while retaining or strengthening the one on the window's border. Or in a similar direction No mockup though, sorry.

Also, removing the ability to switch the header would cause an uproar from the community I think, and with a good cause - it's more logical to have the header always in the same place, but for different windows the header just feels better being on top or on the bottom, and I think it can differ from person to person.

Campbell Barton (campbellbarton) changed the task status from Unknown Status to Unknown Status.Mar 10 2016, 6:41 AM

No resolution or activity in over 3 months,
archiving, listed in the wiki.
Can re-open when we have time to handle this one.

Going through old UI ToDo tasks - this seems fixed with the 2.8 changes. Marking the ToDo item as done.