- User Since
- Dec 15 2009, 3:28 PM (509 w, 1 d)
Sat, Aug 31
Found another misbehaviour with bpy.utils.units.to_value()
When using the Imperial unit system, if the input string is empty, it doesn't produce the expected result which should be 0.0
Specifically, it fails when converting from Metric to Imperial, when performing the division x/0.3048
This of course doesn't happen when using the Metric unit system.
Fri, Aug 23
What about using Right Clicking only on gizmos? Is this too stupid?
This doesn't force Right Click selection, though in a way it defeats the purpose of the Left Click Only.
Left Click select created a lot of problems only because of its ambiguity. You even had to start messing around with thresholds and dragging.
When the mouse is far, it could work as normal, showing the Context menu. Left Click could continue to be used for everything else in all of the interface as expected.
The Right Click on gizmos could be the only exception to the rule, and it would be for a good reason, allowing clicking and dragging without ambiguity, it could be even faster to use.
Jul 6 2019
Jun 30 2019
I did a compilation test and it works fine when adding GPU_blend(true) and GPU_blend(false) to the file ../source/blender/windowmanager/gizmo/intern/wm_gizmo_map.c at the line 446, in the part that forces the antialiasing for gizmos.
I don't have any experience with C nor Blender architecture, so I don't know if that is the proper place for that change.
I investigated a bit further and discovered that this happens when the operator of RENDER_OT_render receives a copy of the current context as an override.
Then, all above symptoms replicate. It only occurs when the display mode is in New Window. With all other display modes, passing the override to the operator works just fine.
You're right. It seems that something was corrupt somehow. By returning all to factory settings it works normally.
Jun 29 2019
May 20 2019
Looking forward for possible solutions on this.
Didn't find any other appropriate place to ask this, but what is the proper way to add antialiasing to custom gizmos?
I'm currently writing my own gizmos for addons, but couldn't find any dedicated property to enable or disable the antialiasing. I'm also interested in the way points are drawn in the 3D view, as these can be square or round.
May 16 2019
May 14 2019
It seems to be fixed now with f070bdd7c9c4
The Options panel was relocated from the Active Tool settings to a new dedicated tab in the sidebar.
May 11 2019
Nov 30 2018
Nov 21 2017
Jul 1 2017
Aug 19 2016
Aug 16 2016
Aug 11 2016
Aug 9 2016
Aug 8 2016
Jun 20 2016
Jun 18 2016
Jun 17 2016
May 24 2016
May 22 2016
May 21 2016
May 20 2016
May 13 2016
May 7 2016
May 3 2015
May 1 2015
Hi. The last time a dev said that to me, he pointed me to BlenderArtists, but that never leads to any result. How are we supposed to collaborate? Becoming a dev?
It may be not a bug from the dev perspective, but from the user perspective, it feels like a bug, because the software is not actually doing what it says it's doing. So, does this mean that no change will be done? even if we know the software isn't doing the right thing?
What's the problem with adding particles lifetime?
Feb 13 2015
I understand. Will make a post in BA as well.
Sorry Bastien. I didn't know. And I think making a post in blenderartists will do no difference at all in development, at least with minor UI aspects like this. Do devs really look into blenderartists forums?