Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2020-08-07Code Style: use "#pragma once" in source directoryJacques Lucke
This replaces header include guards with `#pragma once`. A couple of include guards are not removed yet (e.g. `__RNA_TYPES_H__`), because they are used in other places. This patch has been generated by P1561 followed by `make format`. Differential Revision: https://developer.blender.org/D8466
2020-03-02Cleanup: make remaining blenkernel headers work in C++Jacques Lucke
2019-04-27Cleanup: comments (long lines) in blenkernelCampbell Barton
2019-04-17ClangFormat: apply to source, most of internCampbell Barton
Apply clang format as proposed in T53211. For details on usage and instructions for migrating branches without conflicts, see: https://wiki.blender.org/wiki/Tools/ClangFormat
2019-03-08BKE mesh remap: add utils to add needed cddata mask for source mesh.Bastien Montagne
In some cases (currently, only when using avanced mapping of loops), code needs access to some cddata of the source mesh (CD_NORMAL...). We need a way to inform calling code about that (actual issue requiring this change is fixed in next commit).
2019-02-18doxygen: add newline after \fileCampbell Barton
While \file doesn't need an argument, it can't have another doxy command after it.
2019-02-06Cleanup: remove redundant doxygen \file argumentCampbell Barton
Move \ingroup onto same line to be more compact and make it clear the file is in the group.
2019-02-01Cleanup: remove redundant, invalid info from headersCampbell Barton
BF-admins agree to remove header information that isn't useful, to reduce noise. - BEGIN/END license blocks Developers should add non license comments as separate comment blocks. No need for separator text. - Contributors This is often invalid, outdated or misleading especially when splitting files. It's more useful to git-blame to find out who has developed the code. See P901 for script to perform these edits.
2019-01-28Cleanup: sort forward declarations of enum & structCampbell Barton
Done using: source/tools/utils_maintenance/c_sort_blocks.py
2018-06-21Cleanup: names: data transfer/mesh remap: dm -> me/mesh.Bastien Montagne
That area is now officially purged from the Devil.. errr... DerivedMesh!
2018-06-21Cleanup: nuke DM out of data transfer code.Bastien Montagne
This was actually rather hairy, this code is huge and complicated, easy to make mistakes... Good thing is, it will allow for significant simplification and more (name) cleanup in following commits ;)
2015-07-13Data Transfer: Add an option to 'auto-transform' destination mesh so that it ↵Bastien Montagne
matches best the source one. This allows to match and transfer data between two meshes with similar shape but complete arbitrary different transform. Note that the result will be best if the meshes (more precisely, their vertices) are exact copies of each other. Otherwise, method used can only perform an approximated best match, which means you'll likely get better results if you 'visually' make them match in 3D space (and use 'Object Transform') instead.
2015-03-28Cleanup: redundant struct declarationsCampbell Barton
2015-01-19Make use/computation of lnors consistant.Bastien Montagne
Issue was, when requesting (building) lnors for a mesh that has autosmooth disabled, one would expect to simply get vnors as lnors. Until now, it wasn't the case, which was bad e.g. for normal projections of loops in recent remap code (projecting along split loop normals when you would expect projection along vertex normals...). Also, removed the 'angle' parameter from RNA's `mesh.calc_normals_split`. This should *always* use mesh settings (both autosmooth and smoothresh), otherwise once again we'd get inconsistencies in some cases. Will update fbx and obj addons too.
2015-01-09BKE: Add 'mesh remap' code.Bastien Montagne
This is the (big!) core of mesh transfer data, it defines a set of structures to represent a mapping of mesh elements (verts, edges, polys of loops) between two arbitrary meshes, and code to compute such mappings. No similarity is required between source and destination meshes (though results when using complete different meshes are rather unlikely to be useful!). This code is not bound to data transfer, it is defined to be as generic as possible, and easy to reuse or extend as needs arise. Several methods of mapping generation are defined for each element type, we probably will have to adjust that in future (remove useless ones, add new ones...). For loops, you can also define islands (for UVs e.g.) so that loops of a same destination polygon do not 'spread' across several source islands. Heavily reviewed and enhanced by Campbell, thanks a lot!