Page MenuHome

Color for edges with bevel weight same as selected edges color
Open, NormalPublic

Description

System Information
Windows 10
GeForce GTX 560 SE

Blender Version
Broken: 2.77a

Short description of error
The color for edges with a bevel weight is the same as the one for selected edges (default orange). The color property of bevel weight is non-existant in the user preferences. It draws its color from the "selected edge color" property. If one changes the color for selected edges, the color of beveled edges is also for that color. All other edge properties (crease, active, seam, sharp, etc.) can all be set to a unique color except bevel weight.

I was wondering if this shouldn't be filed as a feature request, but I reasoned that it should be considered a bug, because it makes bevel-weighted edges appear selected even though they are not. In fact, there is no way to distinguish a selected edge from an edge with a bevel weight.

Details

Type
Bug

Event Timeline

Sergey Sharybin (sergey) triaged this task as Normal priority.Sep 14 2016, 2:53 PM

@Philipp Oeser (lichtwerk), are you investigating the report?

@Sergey Sharybin (sergey): yes, would hop on that now [T49343 was taking longer than expected...]

first note though: even though they share the same color (which we could define a new user-preference for), they seem to be drawing in different line width, and unselected edges draw ontop. So they can be distinguished from selected edges.... but anyways, will look into adding new preference for that...

@Philipp Oeser (lichtwerk) : I also just noticed that the edges with a bevel weight will not show in vertex selection mode (they only show in edge or face mode), whereas sharp and creased edges do show in vertex selection mode. Should I file a different report for this?

@Vilko Lafliksyon (Eranekao): can have a look at that, too, guess it's fine to have just one report... will do tomorrow

made edge bevel weights also draw in vertex selection mode D2236: T49347 part two

It is really amazing to see how fast and efficiently this has been addressed. Thank you so much for doing what you do. I don't think the community says it enough but we really appreciate the effort the devs are putting into this great software.

@Vilko Lafliksyon (Eranekao): dont speak too soon, this hasnt been commited yet ;) [those patches are in review, added you as a subscriber there so you can see progress]

@Philipp Oeser (lichtwerk) Yes of course, there's still a long way to go before it makes its way to a final release but even if the fix/feature is dropped, you put some effort into this and you didn't have to, so I reiterate, thanks for what you guys do! And from the looks of it so far, this patch is moving forward nicely :p