Mon, Mar 11
Tue, Mar 5
Thu, Feb 28
Thu, Feb 21
Mon, Feb 18
Since I do not have commit rights, would anyone want to commit this one?
Feb 15 2019
Add test for pulldown menu type.
Putting the enum menu title at the bottom is a bit odd, but seems fine to me anyway.
This is how it always been implemented, my patch does not influence menu title positioning.
But that would also require to write a new widget type, which is far beyond the scope of this patch.
does it also affect color picker-type popups?
It does not, color picker is a different widget type.
Feb 13 2019
Feb 12 2019
Defined RNA property default.
Feb 8 2019
Feb 7 2019
Also what to do if object is linked to collection that is no linked to any scene? Just ignore those?
Jan 20 2019
I discovered context.objects_in_mode which gives a list of objects in current context.mode which is very convenient.
So context.edit_object is redundant and can be removed? Including other mode specific calls (sculpt_object, vertex_paint_object, weight_paint_object, etc.)?
Since multi-object editing is now available in 2.80, it would be convenient to replace context.edit_object with context.edit_objects to get the list of all objects currently in edit mode instead of one active object.
Jan 19 2019
Running bpy.ops.mesh.poke() in the Python console works in 2.8.
Hi William, this report is not about mesh operator, it is about bmesh operator. Hence bmesh.ops not bpy.ops.
Jan 16 2019
Closed by commit rBA0b4cfab541e3
Jan 15 2019
OK, then let's make it tidy:
Jan 11 2019
Hi Simon, your patch does not port all add-on functionality and since there is nothing about that in the description of the task, here is what currently missing:
Jan 3 2019
Dec 29 2018
Dec 22 2018
Microsoft fixed the issue in KB4471324. Blender no longer crashes the system.
Dec 12 2018
Have you tried installing the latest drivers from the NVIDIA website?
Dec 4 2018
Dec 2 2018
Dec 1 2018
Oct 2 2018
In this case function will do some math with the unit scale value
Correction: currently to_string will always assume Unit Scale to be 1.0, so developers would do Unit Scale conversion manually before passing the value to function. Which makes sense, Unit Scale conversion is not complicated and is optional, so please ignore that part.
However it does not make sooo much sense to have this function bpy.utils.units.to_string(1, 'MILLIMETERS') because all it does is appending mm to the number, basically. Also it is not clear what unit the 1 has.
to_string should not be affected by the scene settings (or it should be possible to override them). Or developers would be forced to change scene settings first, before using to_string if they need output in certain units (I hate so much when this happens).
I could not tell from the code changes, does units.to_string support "fixed units"?
We should keep adaptive, even if we change the default away from it. People have been using it and some like this behavior.
Hi Jacques, Brecht, I have a few points I want to address from a user point of view:
Jul 31 2018
Closed by commit rB36389444b03e
Jun 15 2018
May 16 2018
Why not use double side as default?
We are not 10 years ago, PC's are far better now.
Or there will be something better than the back faces?
May 8 2018
@William Reynish (billreynish) I'm not saying unit scale should be removed, I'm saying that to work with different units Blender should move from using unit scale to using display units (or working units like in Maya).
Hi, please let me propose default value for Empty Image Offset property.
Apr 25 2018
Apr 9 2018
Feb 12 2018
First case test_bmesh.blend – coplanar geometry, not intended to work with BMesh solver whatsoever.
Feb 11 2018
Nov 10 2017
Oct 6 2017
Sep 3 2017
Sep 2 2017
Aug 27 2017
Jul 17 2017
Jul 11 2017
...depends on available upper/lower space...
Jun 26 2017
Jun 21 2017
Jun 19 2017
Jun 8 2017
Jun 7 2017
Jun 1 2017
Can this be reverted to the previous behavior before the release? I depend on this very often in my work.
May 29 2017
I can't think of a single use case where handling each vertex is more preferable than island during translate operation. But I can bring a lot use cases for handling whole island in hard surface area, including jewelry modeling.
May 25 2017
Apr 18 2017
Mar 28 2017
Then what are criteria for an empty file?
I think we all can agree that a file with objects, object data, materials and textures cannot be empty.
Mar 27 2017
@Campbell Barton (campbellbarton) as I understand this option performing data cleanup after Factory Settings file is loaded. Which means as soon as Factory Settings would receive new default data—this feature will become obsolete and need to be updated.
Mar 13 2017
Feb 5 2017
Feb 3 2017
Tested latest builds with factory settings on two Windows 10 machines, issue is clearly appearing on both of them.
Feb 2 2017
Windows only bug?
I tried the most recent windows builds: 3ab8895 both x64 and x32, Z hotkey still doesn't work after using F8.
I also tried 6edfa73 for VS 2015 x64, it doensn't work either.
Jan 25 2017
Nov 18 2016
Nov 13 2016
@Bastien Montagne (mont29) that precisely was my point. All I/O add-ons should be updated in order for Blender's "Display Unit" to work in pipeline with other DCCs.
I'm sorry I did not make that clear.
Nov 11 2016
Fixed by rBA7df41339ae89
@Vuk Gardašević (lijenstina) I've prepared the fix already, but OK.
Hi Eugene, I have looked into the problem as I promised and here is what I've found.
Nov 8 2016
@Dalai Felinto (dfelinto) I hope you don't mind that I reopened and updated the task?
Also I can take the assignment if you guys have your hands full.
Nov 7 2016
I am so sorry about that, here is complete steps to reproduce the error:
In that case, would that be acceptable?
Nov 5 2016
Campbell's request: change title from "Print3D" to "Print3D Toolbox".