Width space any menu without ... (3 dots) #81400
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#81400
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Darwin-20.1.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.0.40
Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-01 21:21, hash:
edd1164575Worked: (newest version of Blender that worked as expected)
Short description of error
Width space any menu without ... (3 dots)
Exact steps for others to reproduce the error
MacOS 11 Beta
Width space any menu without ... (3 dots)
See 3 picture you can see ... (3 dots) below
I am deaf/blind (Low vision) on Preferences > Theme on "Text Style" plus Interface on "Resolution Scale (2.00)
Need to fix width to be fit without ...
Added subscriber: @Kent-Davis
Added subscriber: @HooglyBoogly
I'm not sure how this one will be triaged. Currently popovers don't support dynamic width based on the text, it would be nice to support though.
Just so you know, you can hover over the label with a "..." at the end and it will show the full text in a tooltip. I know that's not a perfect solution, but at least it might help until there is one.
No that is not show TOOLTIP while hover mouse cursor.
You're right, sorry about that. It's when you hover over the value / color on the right that the full property name is displayed.
How?
Added subscriber: @Harley
@HooglyBoogly - Kent is changing the interface text size in Preferences / Themes / Text Style so that he can have larger text without also having an enlarged vertical line spacing or having huge icons. This seems like a quite a legitimate use case, although I wish we could do this a bit better.
First, I think we should not allow separate sizing of both "Widget" and "Widget Label" as they both have to be the same or things break in the UI anyway.
Then once we did that we'd have a single "points" value that we could use in combination with dpi and/or Resolution scale when sizing menu, popover, and dialog width. In effect change from a popover width that is "800 pixels wide at Resolution Scale 1.0" to being "the width of 40 ems"
You did not listen me what I said. I have low vision
Need to fix auto width itself in code to fix.
Yes, I understand that perfectly.
Yes, that is in fact exactly what I said, with details on how we could approach doing so.
Ok I am use Macintosh MacOS 11 Beta.
Actually this might be fairly trivial. And would be nice to do for the accessibility issue here, but there are also some internationalization issues it would help with.
Ok
Notes to self: A quick look at this and it seems like it might be easy and make a lot of sense. It cannot be part of the sizing of all block though, more a change in the way that we calculate the widths. For this though we'd need to be able to easily compare the current text size against "normal" and that will be available with D9107 in 2.92 (probably).
@Kent-Davis - Hey, I was hoping that you can tell me a few things about how you run your blender:
What is your resolution scale? Edit / Preferences / Interface / Resolution Scale
What is your line width? Edit / Preferences / Interface / Line Width
What the point sizes you set Edit / Preferences / Themes / Text Style
Added subscriber: @lichtwerk
@Harley I am sorry I do not believe you said "CAN'T" no way.
Everything possible to fix. I has been send report ticket few years and send many tickets.
5K retina display 27" iMac for Mac only. Not for Windows.
Do you have Mac?
Resolution Size 2.00
Line Width your wrong answer.
I can't read "normal size" sorry. They need to work on code to be fit.
@lichtwerk know.
I didn’t say “can’t”.
Thanks for the details of your system and settings, so I can test identically.
Yes, and I will see if I can improve things for you.
Oh ok.
Do you have Macintosh computer?
Now you see "Cannot" same "can't"
You are just misinterpreting a comment I made to myself about possible implementation. I am saying that I have to do it one particular way and not in some other way.
Recreating "Before and After" captures based on your images above. The top of each image is the part that you highlighted in blender as it is now. The bottom of each shows how it looks after my own changes I am working on:
Now I see before (me) and after (you) I got it. Are you use Macintosh?
(More Space) on System Preferences > Display
A patch can be found here: https://developer.blender.org/D9132
You are wrong answer you did not put Mac information.
I can tell this link for Windows only.
Please do focus on Mac.
That is incorrect Kent. The display of blender is the same on all platforms and the patch I have created will effect Mac, Windows, Linux, and everything else.
No. Windows display and Macintosh display is different. Think about iMac have 5K. do you have Macintosh yourself?
Windows and Linux up to limit number example 2048.
Macintosh can be 6400 x 3600 pixels.
I do ask you. Do you have your iMac yourself?
No, I do not. But as far as your issue is concerned there is no difference. Please stop wasting time with this line of questioning. If you are able to compile blender from source, then please test the linked patch. Otherwise you'll have to wait for others to test, approve, and then hopefully you will find your problem fixed one day in a blender release.
I don't know how to fix code inside the Blender 2.91 Alpha
Then you are going to have to trust me that the patch fixes the issue that you show in this ticket, and wait for it to be (hopefully) approved and committed.
I am wait for next Daily Build will be October 6, 2020. I am in USA Pacific Time California.
The patch is not committed so it will not be on a daily build. If you watch the patch that it is on you can following its progress from evaluation, through corrections, approval, and committing. It could take days, weeks, or longer depending on how many people test, how busy everyone is, etc.
I will not follow patch for Windows only.
I can do follow patch for Macintosh only.
I am wait for some one use Macintosh to answer.
I see "wmWindow *window = CTX_wm_window(C);" is not match on Macintosh. I ignore it.
Ignore whatever you want, but you are still wrong. A "wmWindow" is blender's structure to hold a window on all platforms. It has nothing to do with the Windows operating system. Again, please stop this line of questioning. You are making incorrect assumptions because of a lack of understanding of the blender source code. I don't have time to answer these off-topic questions here.
Added subscriber: @ankitm
I found your name @ankitm I let you know read above because they focus Windows they don't understand Macintosh. They force me to check link I ignore as well about Windows. Would some one deeply inspect on Mac only. Not for Windows.
@Kent-Davis the code is talking about this window https://en.wikipedia.org/wiki/Window_(computing)
not this Windows: https://en.wikipedia.org/wiki/Microsoft_Windows
Also, remember that we have a "Window" menu in all macOS apps :)
@ankitm -
In a nutshell @Kent-Davis increases his Themes/Text Style font points to make everything more readable because of visual problems. And as that point size is increased, independently of Resolution Scale, some things like the width of popovers become too narrow. This patch solves that but for some reason he doesn't believe me (and can't test himself) and thinks this will work only for Windows (because of some object names). Not sure why he thinks I'm lying to him when I am only trying to help him, but it is what it is... LOL
Changed status from 'Needs Triage' to: 'Confirmed'
Thank @ankitm see my MacOS 11 Beta on System Preferences > Display > More Space (6400 x 3600)
27" 5K
@HooglyBoogly Oh well you did choice for Windows 10 did not show Macintosh. Do you have your own iMac ?
As mentioned, the problem you are reporting is not specific to Macintosh. And the fix referenced affects all platforms, including Macintosh.
Windoes 10 and Macintosh is different.
That is true, but completely irrelevant. The problem you have reported affects all platforms, and the referenced fix applies to all platforms.
This issue was referenced by
bdad412fa7Changed status from 'Confirmed' to: 'Resolved'
@HooglyBoogly Congratulation there for Mac resolve. I can show you screenshot for Mac only.
Glad things are working better for you. That one popover though, for "Cursor" is problematic even with default sizes, so I will have to widen that separately. Here it is with default font settings and sizes:
@Harley Oh I see no problem.
I just mean that the ellipsis you see after "Inverse Cursor" I also see in regular usage. We should be able to fix that too.
Sure no problem.