- User Since
- Mar 7 2010, 9:01 PM (476 w, 2 d)
@Brecht Van Lommel (brecht): I really like the look of this...
@Brecht Van Lommel (brecht): My current thinking is we can do a gaussian blur of the alpha channel...
Sun, Apr 21
This is now complete and can be tested and evaluated.
Sat, Apr 20
A few comments, possibly all dumb, so no laughing... LOL
Fri, Apr 19
A patch for this particular issue (with outliner_draw_tree_element) is now here:
@Dalai Felinto (dfelinto): This works fine. Does this approach work for you?
I agree, but couldn’t find (from what I could understand from that area) another way of fixing that. I don’t really know how important that performance regression could be, nor how much weight to give to the original complaint.
Wed, Apr 17
This is now only WIP.
Tue, Apr 16
I thought you’d like that. LOL
Mon, Apr 15
Some notes on this, for me or others...
I will probably look at this one next. Look like fun.
Sun, Apr 14
Not strictly necessary, but extremely helpful, because it is a royal pain to keep track of it during menu creation.
That is awesome news!
AFAIK we are probably going to lose both "Collections visibility" and "Object type visibility" from there before too long, so that should lea
Where was this written?
Object type visibility is useful to keep there because the icon gives a quick visual hint if any types are un-selectable or hidden (without having to open the popover).
@Gavin Scott (Zoot): I'd love to do a Preference for "words vs. icons-based UI"
Sat, Apr 13
Fri, Apr 12
@Andrzej Ambroz (jendrzych): does orange backdrop mean "this item is in Edit Mode"?
@Andrzej Ambroz (jendrzych) : Ha! You've changed it...
Sorry, I think you would have to dumb it down further for me because I am still not getting it. When I look at that third mockup of yours I only see more colors.
@Christoph Werner (Taros) : not sure about the outline. Filigree outlines are always "critical"
With this change:
Another small change:
@Andrzej Ambroz (jendrzych) : have to ask You to provide me a screenie depicting situation
Thu, Apr 11
@William Reynish (billreynish): I had actually hoped we could make use of this gutter on the left for selection purposes.
This update removes the unnecessary space to the left of the tree when in View Layer mode
@Andrzej Ambroz (jendrzych) : The grey circle backdrop makes icon look muddy and dull
@Andrzej Ambroz (jendrzych): is there a possibility to change the backdrop circle's colour via Preferences panel? I can't find it. Would like to check out other colours. Deep black first.
This patch was updated for two reasons:
This patch is meant to only propose some visual changes, separate from functional changes, to avoid getting into bikeshedding weeds. I think how it looks right now makes it all seem a bit more complicated than it really is. I mostly wanted something we could use to look at and then decide what parts we might like changed or not. If keeping everything I think I'd rather hide the hierarchy line code behind a conditional rather than delete that section as this patch currently does.
Wed, Apr 10
The patch now includes the fix from this patch:
It's not a theme issue, but a problem in how objects are evaluated to whether they are selected or active.
Tue, Apr 9
Until this problem is fixed properly, we should make the region overlapped areas have a very very small amount of opacity, rather than zero. Just enough to give a hint that something is there. Just on the default theme.
Sun, Apr 7
The selected/active states better reflect the same states in the 3D View using the same colors
That is a danger of making entire categories of icons one color or another (Preferences / Themes / User Interface / Icon Colors). We might want something like modifier icons in one location to be white, in another to be black, and another to be blue. In this case we are making them all black in the "Blender Light" theme so they look a certain way in the Outliner. But then they cannot be seen in the Modifiers list.
@Gavin Scott (Zoot): we could emit mouse-over tooltips for all these
- A line in the diff was adding an unwanted whitespace char.
- Hiding item now (again) dims the name of item.
- Tweaks to spacing between icon and name and name and icons on same row.
- Tweaks to the opacity of child items versus displayed on merged row
Sat, Apr 6
The vertical bar separator on the rows is removed.
Fri, Apr 5
Thanks @Brecht Van Lommel (brecht). I think I see it all now.
@William Reynish (billreynish): Is there a document somewhere that I can look at to understand what the intentions are with the highlighting?
could even completely get rid of the separator pipe between the object name and the child icons...
Thu, Apr 4
@LazyDodo (LazyDodo): they did away with the up button all together
Wed, Apr 3
@Clément Foucault (fclem): Thanks for helping to "teach a man how to fish". It is appreciated.
GPU_line_width already takes into account U.pixelsize...
Fixing mistake regarding LineWidth. The width of the lines now does properly follow current U.pixelSize.
Changed to GPU_PRIM_LINE_STRIP instead of GPU_PRIM_LINES since drawing only bottom and right edges and they are connected.
A patch can be found here:
@ThinkingPolygons (ThinkingPolygons) > Are those lines themeable?
No problem. Will make a patch. Tonight? Have a bit of (real) work to do and then a mountain bike ride. LOL
Tue, Apr 2
Another option is to leave the width as it is now, but make the lines easier to see.
There are definitely things that can be done. But not sure if you would prefer some captures first maybe?
I'm not seeing it exactly as described. It says "there is no separating line to separate the various views" but the "Before" image definitely shows a darkened edge separating the four quad views.
Sorry to be so... wordy. Never know how much detail to get into with these things. LOL
So in case you want this done, this is the same patch but also CORRECTS the issue with isStartedFromCommandPrompt() so that function can be used as the name implies.
Having a quick look at isStartedFromCommandPrompt()...
This change makes it so the console "close" button is only ever disabled if Blender was not started from a command prompt.
Brecht, you are exactly right: it should be explicit.
It's been a while since I poked around in there, but I *thought* the general problem is that our "temp" windows, like standalone Prefs, are not created as proper child windows. I think all windows (main, secondary, temp) are made with the same ghost createWindow and the "parent" for all of them is set to zero. So our "child" windows are really more like siblings. So it doesn't matter what we set for things like "TOP_MOST" since we don't have the relationship set right.
Mon, Apr 1
@LadyDodo: Love xkcd "workflow" one! But there is always Task Manager. ;-) But note that this does NOT disable the close if the Blender session was started from a command prompt.
A patch that does this can be found here:
Sun, Mar 31
This is just a Windows thing, right? Just removing the "close" button would eliminate all issues with it.
Fri, Mar 29
Mar 14 2019
@Clément Foucault (fclem) : to be really honest, I know next to nothing about openGL so was playing with that fairly blindly. It did fix my issue, but I don't have enough related knowledge to know it would not affect anyone else adversely. Which is why I abandoned that patch.
Yes, it does the same thing here. I'm assuming it is video card-specific (mine is a GeForce GTX 745).
Mar 7 2019
I definitely agree it would be a shame.
Mar 4 2019
I don't find it a big improvement either