| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
- MTexPoly structure & layer type.
- The 'Mesh.uv_textures' layers.
- DerivedMesh TexFace drawing.
- Scripts & UI.
|
|
|
|
|
|
also set_source_files_properties() wasn't working for rna_*_gen.c files,
set dna.c and generated data files with generated property too.
|
|
paste errors), also remove BKE_script.h
|
|
args.
|
|
API.
It was an error how index of requested layer was searching: iterating used to start
from the beginning of data layers datablock, not from index at which requested
layer type actually begins.
|
|
can type in any value, and only when sliding the number value there is a limit.
It was already possible to assign any value to a socket with node linking, so
this shouldn't cause any new issues.
Also raised the limits on the math nodes, with a patch by Agustin Benavidez.
|
|
sync. (entering editmode would show the wrong UV layer)
|
|
Note about long lines: I did not touch to two pieces of code (because I don’t see any way to keep a nicely formated, compact code, with shorter lines):
* The node types definitions into rna_nodetree_types.h
* The vgroup name functions into rna_particle.c
|
|
variable so assignment failed.
|
|
on access in editmode
just missing NULL checks on face data.
|
|
Addresses:
* C++ comments.
* Spaces after if/for/while/switch statements.
* Spaces around assignment operators.
|
|
|
|
- use consistant header guards
- correct doxy comments
- remove ED_toolmode.h (unused)
|
|
Warning! Tesselation uvs or vcol data got out of sync, "had to reset!
This would happen on every editmode edit with UV's and wasn't too reassuring that blender was handling uvs/vcols correctly.
From looking into the problem I found that creating the undo mesh would act as if it was tessellating the existing mesh each time and complain that the data was out of sync, when infact the mesh was just created and being filled in.
Also, allocating uv and vcol customdata arrats for tessfaces isn't needed for undo mesh, so save some memory and dont allocate these in the first place.
|
|
customdatalayer collections (especially as upcoming bmesh cycles changes will add a few more such collections)
|
