Page MenuHome

screen area border not matching clickable area if thick lines is selected
Closed, ResolvedPublicKNOWN ISSUE

Description

System Information
Operating system: Windows 7 64bit
Graphics card: GeForce 1060

Blender Version
Broken: blender-2.80.0-git.ec471a9b1c14-windows64 (built 16. Feb. '19)

Short description of error
in the preferences, switching "Line Width" from "Thin" to "Thick" makes
borders between screen areas wider by 4 pixels, but only 2 pixels wider
for the mouse cursor to grab it

Exact steps for others to reproduce the error

  1. start blender, set "Line Width" to "Thin" in the preferences, if it is not already
  2. go to any screen area's border, notice that it is 3 pixels wide and you can grab it pixel-perfectly
  3. switch "Line Width" to "Thick"
  4. again look at any border, notice how it is 7 pixels wide but you can only grab the inner 5

not sure what to add, fixing this would obviously make it require less attention to resize areas
or for the right-click split/join operation.

cheers, boogie

Event Timeline

I thought this “line width” was intended to only affect lines in the 3D editor? With it changing everything it makes it more complex to determine how big something is since this is independent of user scale. We currently have a very large number of unnoticed “off by a pixel” errors because of this.

For an example think about having to know the width of a some widget. Without line-width it is trivial to just work in ui_widget_units since these are changed with user scale. But adding line width makes the calculation complex since it depends on how many borders it has. You might have a user scale of 1.5 and thick lines or 2.0 and thin lines. Yikes.

Maciej Jutrzenka (Kramon) lowered the priority of this task from 90 to 30.Nov 26 2019, 5:10 PM
Maciej Jutrzenka (Kramon) edited projects, added BF Blender; removed BF Blender: 2.8.

Does this happens in 2.81?

Philipp Oeser (lichtwerk) raised the priority of this task from 30 to 90.Dec 5 2019, 3:52 PM

Needs another look imho

The cause of this is a bit complex. I have more detailed information about it, and a patch that corrects, it here https://developer.blender.org/D4947

But because of the complexity of the underlying problem my changes are fairly drastic, which makes it less likely to be accepted. I was just unable to find a quick and simple solution that worked good enough.

Germano Cavalcante (mano-wii) lowered the priority of this task from 90 to Low.

The cause of this is a bit complex. I have more detailed information about it, and a patch that corrects, it here https://developer.blender.org/D4947

In this case I'm assigning this report to you (if you don't mind).

Julian Eisel (Severin) changed the subtype of this task from "Report" to "Known Issue".Jan 24 2020, 11:28 AM

Since this is not really a bug, more of a usability issue, I'm setting this to "Known Issue". I intent to look at Harley's patch soon.

Indeed, @Harley Acheson (harley) already solved this problem a long time ago. We just need to merge his changes and we are golden.

Don’t get too excited. My patch is only useful if someone (smarter) refactors the corner-drawing. https://developer.blender.org/D4947

Philipp Oeser (lichtwerk) claimed this task.

Thx noting @Harley Acheson (harley), will close then.