- User Since
- Apr 18 2016, 11:44 PM (161 w, 6 d)
@Harley Acheson (harley) we can’t consider multi-object the ‘normal’ case in terms of visual indication, because:
Cannot reproduce any issue with this file. It seems to render normally and animation playback works.
This report is too vague. We will need a blend file and specific steps to reproduce.
I can confirm this. What you mean by 'gizmo' isn't what we internally call a gizmo though. It's the cursor + connection line that is missing in this case.
Currently, this still uses the same indication method as before, it just promotes it so you can already see it while hovering:
Great, this is excellent.
Fri, May 24
Indeed, Knife tool seems to perform worse with extreme wide angle view points, as in your file. Unsure how to triage.
Indeed, can confirm. Quite strange.
open the file.
@Campbell Barton (campbellbarton) I assume this is related to recent changes to gizmos.
Cannot reproduce any of the issues with this file. Could be a GPU or driver issue
Cannot reproduce this. Can you post your blend file for testing?
You'll need to post a blend file for testing.
This is a real nice improvement that greatly improves visual clarity:
Thu, May 23
Well, as far as I can see, it works as intended. When using the Box Select tool, you drag to select, hold Shift to extend and Ctrl to subtract. That is how it's intended to work. Middle mouse click is not applicable in this case - what matters is holding Shift or Ctrl.
Indeed, doesn't appear to be a bug.
I don't follow, unfortunately.
As far as I know, this is not a bug.
Also, I should add that I can see you are using an older version of Blender 2.8.
Your model doesn't have a UV map:
Cannot reproduce here on maxOS 10.14.
This is not a bug but a design issue.
I don’t think this was ever supported by anything other than pulldown menus. The issue is that, if it were enabled for enums and popovers, you would easily open then accidentally when just navigating over the Properties editor, for example.
Ah ok. That was quick ;)
This shortcut is used by the OS.
This commit appears to break the rotate gizmo.
Wed, May 22
This relates to the issue we discussed with modifier keys and gizmos.
The issue with horizontal text, is that it can eat into the content area. If you go to 10.000 for eg, it takes up a lot more horizontal space then, which the editors need to account for.
Don't know how to triage - it's not really technically a bug, but the defaults probably should be changed.
@Campbell Barton (campbellbarton) Yes, will do.
Yes, can confirm now.
I cannot reproduce the issue. Convert To seems to work fine here.
@Campbell Barton (campbellbarton): feel free to re-assign if this is not for you.
Tue, May 21
Yeah I guess it doesn’t take the UI scale into account
The other reason it works this way, is because on smaller displays there will then be enough space for all the items in the header.
I guess then yes, it should be enabled by default, if it only affects Macs anyway.
@Jacques Lucke (JacquesLucke) Thanks for fixing. I think any item using pixels should be multiplied by the UI scale.
There is no right or wrong, it's just different:
Tested - seems to work well.
Also, what is the definition of 'wrong'? On macOS, scrolling is opposite from some other platforms.
I guess the Minimum Grid Spacing doesn't take UI scale into account?