Why are you even talking about something that clearly you have no experience with.
Damn, this is a joke really. 
2 Likes
man, youāre just trying to force yourself to find faults that are actually distortions of evidence that this change has 100% advantages ā¦to say:
āI do not want to change my mind, Iām lazy to unlearn and relearnā
1 Like
Quit the (baseless) Ad-Hominem
Iām not lazy, I would have nothing to unlearn or relearn, because I use those types of sliders in other programs all the time. Iām using some right now.
And they suck.
If Iām changing a value, I either know the value I want, or Iām looking at feedback from the program to find the value I want.
In the first instance, with these kinds of sliders, you never land on the value you want, meaning you have to drag around anyway.
Even then, when you reach near the number you want, most of the time the increment itās ticking up and down by will leave it at something like 50.21 or so when youāre trying to get 50 (assuming all the factors even get it that close, like the mouse sensitivity, or your ability to move the mouse by a tiny fraction, whilst holding a mouse button down, I might add!).
But then you go to enter in a numerical value and find itās a pain in the ass to change the value numerically anyway, because you have to double click - meaning the program is going to change the value, causing a possibly time intensive update, before even letting you change the value to the actual value you want. Or maybe youāre lucky and the program left a 3 pixel wide space where the āIā cursor pops up and you can single click to edit the number, assuming you donāt miss it.
The only other use for these sliders is moving along them during realtime updates to watch the feedback and find the right value. Which the click+drag functionality is perfect for already. Or, trying to get ballpark values for something when you donāt have immediate feedback because things are laggy or something else delays the feedback like rendering. In this last instance, itās slightly faster, but thatās one out of three use cases for the slider, and a use case where things are assumed to not be happening fast (youāll be waiting for feedback) anyway.
2 Likes
at present ā¦ you never used shift + drag
or ctrl + drag to set more precise parameters?
it would be the same identical thing for the other method ā¦
trust meā¦
the current method is slow which makes me sleep ā¦
and Iāve been using blender for 20 years
and I recognize that it is slow,
It is a fact that anyone can check in 2 minutes.
1 Like
The items on this list are inverted now?
It used to be the other way around.
3 Likes
I absolutely love this thread. Papercuts really are deadly in large number, with enough of them you can bleed to death. This thread is full of so many great little things that could be improved in Blender (some of which have already been fixed which is great). Little changes like these make a huge difference in total.
1 Like
All menus open either towards the top or bottom depending on the available room (which explains that this particular dropdown changed recently because 3DView header was moved to top by default), and their items are ordered from āstart to endā, ie from button to wherever the dropdown is expanded, in this case towards the bottom. Iām personally not a fan of arranging things this way, as I tend to remember direction over ordination (pie menus!), and I would prefer dropdown items be fixed, whether or not they open towards the top or bottom.
please add some separation thickness to quad view
17 Likes
not sure whether this is a papercut a pure bug but hereās the issue:
when an object is linked to only one collection, unlinking it from its collection using the properties panel makes it become orphan data, which make it disappear from the scene and the outliner and remain unusable. wouldnāt it make more sense to link it to the default scene collection?
1 Like
When you work on nodes and you scale out its very difficult to grab the input/output points.
In fusion 9 they make it that the scale of the node points are scale with the view scale.
I miss also that the grab radius is greater than the point icon. (red radius in the pic)
that make the entire workflow much faster.
8 Likes
1 Like
Hell yeahā¦ also 
2 Likes
oh please add a bug report about remembering values of insert extrude bevel spin etc. Pablo just mention it as a bug ^)
Feel free to report. 
https://developer.blender.org/maniphest/task/edit/form/1
Shouldnāt duplicating a collection make copies of everything inside the collection, instead of linking the already existing objects to the new collection?
I just saw Pabloās video Blender Today, and showed that now we can disable the animation framing when we enter the local view, and that is a very convenient option for the workflow.
But what I think, is that keeping this option too hidden between the keymaps by looking for the ālocal viewā shortcut and detach āframe selectedā to disable it, is wrong.
I think it should be an option in the preferences under the ānavigationā preferences, because it is a very important option.
A post was split to a new topic: Strange gizmo via hotkey
I came to the conclusion that it is not a good solution to hide more active tools under a button, after months and months of testing of blender, I am only now discovering by chance, the existence of this interesting and useful tool ā¦
I could not have easily imagined that there was an active secondary tool for scaling objectsā¦
we need a solution to make the āsecondaryā tools more accessible
5 Likes
Maybe because your theme sucks, and you can barely see the arrow? 
4 Likes
yes I can not blame you ā¦ I noticed now that the theme sucks ā¦ but I remain convinced the same that these secondary tools are a bit too hidden
1 Like