| Age | Commit message (Collapse) | Author |
|---|
|
|
|
(even though the other related functions are not following this rule ... How I miss a code refactor dev!)
|
|
|
|
|
|
blo_do_versions_after_linking_280
|
|
|
|
|
|
- mixing of old & new APIs
- vertex format mismatch
|
|
|
|
Replace outlined circle (24 vertices) with a point sprite (1 vertex).
Replace one todo with another todo.
|
|
|
|
D2361 by @punya, part of T49043
|
|
plus manual rna fixup
|
|
Conflicts:
source/blender/blenkernel/intern/depsgraph.c
source/blender/blenloader/intern/versioning_270.c
source/blender/depsgraph/intern/builder/deg_builder_relations.cc
source/blender/makesrna/intern/rna_main_api.c
source/blender/makesrna/intern/rna_particle.c
|
|
RNA definition.
PARM_PYFUNC_OPTIONAL is only useful in definition of callbacks for
registrable types...
|
|
parameters!
Both found cases where luckily harmless, though...
|
|
internal flags.
This gives us 9 flags available again for properties (we had none anymore),
and also makes things slightly cleaner.
To simplify (and make more clear the differences between mere properties
and function parameters), also added RNA_def_parameter_flags function (and
its clear counterpart), to be used instead of RNA_def_property_flag for
function parameters.
This patch is also a big cleanup (some RNA function definitions were
still using 'prop' PropertyRNA pointer, etc.).
And yes, am aware this will be annoying for all branches, but we really need
to get new flags available for properties (will need at least one for override, etc.).
Reviewers: sergey, Severin
Subscribers: dfelinto, brecht
Differential Revision: https://developer.blender.org/D2400
|
|
Also use proper ID_NEW_REMAP macro in BKE_rigidbody_world_groups_relink()!
|
|
Was a waaaaayyyyy to much generic name for such a specific func, renamed
to much more descriptive BKE_libblock_relink_to_newid().
In near future (few weeks, to limit as much as possible silent mismatch
in branches), will rename BKE_libblock_relink_ex to BKE_libblock_relink,
this is the real generic data-block relinking func!
|
|
BKE_libblock_relink_ex instead.
|
|
scene
use tag to make sure we call each object only once
|
|
I'm using the flags in the objects instead of bases.
|
|
|
|
When control object is used we need to known our own transformation as well.
|
|
It is required to have world-space bone position, which consists of armature
object transform and local bone transform.
|
|
Accidentally included some changes from workspaces branch.
|
|
|
|
|
|
//ui_item_enum_expand// function replaces all pie menu's sub-layouts with radial layout. It should replace only root layout.
To reproduce the issue paste the code in Blender's text editor and press Run Script button.
```
import bpy
class VIEW3D_PIE_template(bpy.types.Menu):
bl_label = "Select Mode"
def draw(self, context):
layout = self.layout.menu_pie()
layout.column().prop(
context.scene.render.image_settings, "color_mode", expand=True)
def register():
bpy.utils.register_class(VIEW3D_PIE_template)
def unregister():
bpy.utils.unregister_class(VIEW3D_PIE_template)
if __name__ == "__main__":
register()
bpy.ops.wm.call_menu_pie(name="VIEW3D_PIE_template")
```
Differential Revision: https://developer.blender.org/D2394 by @raa
|
|
Was also affecting object linking.
|
|
buffer.
Reading rest of the code, it's obvious we want to start à YOFF lines
from start of rect2i, so we have to also multiply by number of
components.
Also did some minor cleanup.
|
|
Code was not accounting for possibilities that width or height of given
buffers may be smaller than XOFF/YOFF...
Note that I seriously doubt that drop code actually works (as in, gives
expected results) when applied to tiles like it seems to be done
currently, but this is much more complex (and involved) topic.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Otherwise it's possible to cause infinite update loop in Cycles viewport.
Gets a bit messy logic, need to revisit this..
|
|
|
|
|
|
Problem was setting prev/next faces for edges around
a vertex on valence-2 vertices.
|
|
|
|
This allows this pointer to be used, otherwise the pointer is not written
|
|
|
|
|
|
This kind of keeps threads "warmer" and should in theory give better
cache coherency bringing some %% of speedup. It was already tested
few months ago and it gave few % speedup in barber shop, but was
reverted due to some bone popping. The popping is now fixed so it
should be fine to use new scheduling policy.
|
|
|
