The 'View' text and gizmos are not visible on a bright background #57574

Closed
opened 2018-11-02 03:30:59 +01:00 by Martin Capitanio · 16 comments

Blender Version
git tip 1f4068214f

Short description of error

I think they also should have a (transparent) grey background bar.

image.png

**Blender Version** git tip 1f4068214f6efa79d71419dba1b2a89b9179405b **Short description of error** I think they also should have a (transparent) grey background bar. ![image.png](https://archive.blender.org/developer/F5332209/image.png)

Added subscriber: @capnm

Added subscriber: @capnm
Member
Added subscribers: @WilliamReynish, @pablovazquez, @lichtwerk
Member

Not sure this is a bug?
Looks like we have a transparent (white) circle surrounding gizmos already (text doesnt). Unsure what a good solution would be here.

I'll also mention the related #54723.

maybe @venomgfx , @WilliamReynish can comment?

Not sure this is a bug? Looks like we have a transparent (white) circle surrounding gizmos already (text doesnt). Unsure what a good solution would be here. I'll also mention the related #54723. maybe @venomgfx , @WilliamReynish can comment?
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Pablo Vazquez self-assigned this 2018-11-02 13:07:43 +01:00
Member

It's not a bug. It's a known limitation with white labels on white background and it's been there for decades way before 2.8 or 2.5 even. Solution would be to add a drop-shadow or gray box around it but it would make it look like dropdowns which are interactive, so it's not that simple.

Please use [Right Click Select ]] for proposals and mockups on how to fix this or make a [ https:*devtalk.blender.org/c/user-feedback | thread in DevTalk (the issue is already reported there by the way).

It's not a bug. It's a known limitation with white labels on white background and it's been there for decades way before 2.8 or 2.5 even. Solution would be to add a drop-shadow or gray box around it but it would make it look like dropdowns which are interactive, so it's not that simple. Please use [Right Click Select ]] for proposals and mockups on how to fix this or make a [[ https:*devtalk.blender.org/c/user-feedback | thread in DevTalk ](https:*blender.community/c/rightclickselect/) (the issue is already reported there by the way).

It's not a bug, but it's an issue we should fix. The icons should be dark so they are visible on the dark circles. We can do this via the the new icon category themes. We just need to add these to a separate icon category.

It's not a bug, but it's an issue we should fix. The icons should be dark so they are visible on the dark circles. We can do this via the the new icon category themes. We just need to add these to a separate icon category.

Looks like we have a transparent (white) circle surrounding gizmos already (text doesnt). Unsure what a good solution would be here.

I think a grey circle and grey text background box (maybe transparent) it would be better and more consistent. See the other UI elements inside the view.

> Looks like we have a transparent (white) circle surrounding gizmos already (text doesnt). Unsure what a good solution would be here. I think a grey circle and grey text background box (maybe transparent) it would be better and more consistent. See the other UI elements inside the view.

That would work too. I don't mind if we do bright icons on dark circles or the other way around.

That would work too. I don't mind if we do bright icons on dark circles or the other way around.
Member

Added subscriber: @jendrzych

Added subscriber: @jendrzych
Member

Gizmos bckgrnd - mockup_1.png
Gizmos bckgrnd - mockup_2.png
Semitransparent grey backdrop works better in more cases than semitransparent black or white, just because the grey I used in the mockup is the same that the top header uses. Its’s better to have some degree of contrast between the 3D View’s background and the top header to differentiate those two regions. An outline is not necessary, but could help in those extreme cases, when 3D View content’s colour is close to the backdrops’ luminosity - the backdrop will simply “dissapear” as I depicted in my second mockup (the one in which backdrops with icons overap with tne top header).

![Gizmos bckgrnd - mockup_1.png](https://archive.blender.org/developer/F5336488/Gizmos_bckgrnd_-_mockup_1.png) ![Gizmos bckgrnd - mockup_2.png](https://archive.blender.org/developer/F5336492/Gizmos_bckgrnd_-_mockup_2.png) Semitransparent grey backdrop works better in more cases than semitransparent black or white, just because the grey I used in the mockup is the same that the top header uses. Its’s better to have some degree of contrast between the 3D View’s background and the top header to differentiate those two regions. An outline is not necessary, but could help in those extreme cases, when 3D View content’s colour is close to the backdrops’ luminosity - the backdrop will simply “dissapear” as I depicted in my second mockup (the one in which backdrops with icons overap with tne top header).

Actually, the left mock-up looks good, the outlines are annoying.
I think it does not matter if the backdrop disappears. As long as the (white) text is still readable and the symbol is visible, the grey backdrop loses its original function.

Actually, the left mock-up looks good, the outlines are annoying. I think it does not matter if the backdrop disappears. As long as the (white) text is still readable and the symbol is visible, the grey backdrop loses its original function.

Transparent black or dark grey both will work, yes. I would avoid adding outlines to the circles - it makes the whole thing too complex.

Transparent black or dark grey both will work, yes. I would avoid adding outlines to the circles - it makes the whole thing too complex.
Member

My point is to use gray colour for backdrops, as it is done with transformation info in top left corner of 3D View editor. Outline is not needed in most cases.

My point is to use gray colour for backdrops, as it is done with transformation info in top left corner of 3D View editor. Outline is not needed in most cases.

Although Pablo very kindly marked this task as Invalid, the problem was IMO resolved in:
ef42dcd31e
UI: Darken the backdrop of navigation gizmos.
and
df0058061d
UI: Soft drop shadow on 3D Viewport info text.

image.png

Thanks.

Although Pablo very kindly marked this task as Invalid, the problem was IMO resolved in: ef42dcd31e773b4c2c7ee5f6ef220ea3ce03bf76 UI: Darken the backdrop of navigation gizmos. and df0058061d599ce45dad3589299349ca6f5813b9 UI: Soft drop shadow on 3D Viewport info text. ![image.png](https://archive.blender.org/developer/F5349247/image.png) Thanks.
Member

In #57574#549528, @capnm wrote:
Although Pablo very kindly marked this task as Invalid, the problem was IMO resolved in:
ef42dcd31e
UI: Darken the backdrop of navigation gizmos.
and
df0058061d
UI: Soft drop shadow on 3D Viewport info text.

image.png

Thanks.

I marked it as invalid because it's not a bug and definitely not a crash (the only kind of reports allowed at this moment). But then I felt bad about it and spent my Friday night fixing it.

> In #57574#549528, @capnm wrote: > Although Pablo very kindly marked this task as Invalid, the problem was IMO resolved in: > ef42dcd31e773b4c2c7ee5f6ef220ea3ce03bf76 > UI: Darken the backdrop of navigation gizmos. > and > df0058061d599ce45dad3589299349ca6f5813b9 > UI: Soft drop shadow on 3D Viewport info text. > > ![image.png](https://archive.blender.org/developer/F5349247/image.png) > > Thanks. I marked it as invalid because it's not a bug and definitely not a crash (the only kind of reports allowed at this moment). But then I felt bad about it and spent my Friday night fixing it.

I marked it as invalid because it's not a bug and definitely not a crash (the only kind of reports allowed at this moment). But then I felt bad about it and spent my Friday night fixing it.

At least both of us didn't waste our time uselessly and Blender got better :-)
Thanks.

> I marked it as invalid because it's not a bug and definitely not a crash (the only kind of reports allowed at this moment). But then I felt bad about it and spent my Friday night fixing it. At least both of us didn't waste our time uselessly and Blender got better :-) Thanks.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#57574
No description provided.