archive/blender-archive
Archived
1
1
Fork 0
Code Pull Requests Packages Activity

return typle for mathutils slice's.

Browse Source 
The main advantage with this is that its close to twice as fast to do 'vertex.co[:]' then 'tuple(vertex.co)', this is common for writing a vertex array.
the correct python behavior in this case is to return a copy of the original type, however euler and quats don't support different sizes so we cant do so easily.
This commit is contained in:
Campbell Barton
2010-12-24 03:51:34 +00:00
parent 47fc52f839
commit 2dcfa5acf9
5 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
source/blender/python/generic/mathutils_euler.c
View File

@@ -443,7 +443,7 @@ static int Euler_ass_item(EulerObject * self, int i, PyObject *value)
//sequence slice (get)
static PyObject *Euler_slice(EulerObject * self, int begin, int end)
{
PyObject *list = NULL;
PyObject *tuple;
int count;
if(!BaseMath_ReadCallback(self))
@@ -452,14 +452,14 @@ static PyObject *Euler_slice(EulerObject * self, int begin, int end)
CLAMP(begin, 0, EULER_SIZE);
if (end<0) end= (EULER_SIZE + 1) + end;
CLAMP(end, 0, EULER_SIZE);
begin = MIN2(begin,end);
begin= MIN2(begin, end);
list = PyList_New(end - begin);
tuple= PyTuple_New(end - begin);
for(count = begin; count < end; count++) {
PyList_SET_ITEM(list, count - begin, PyFloat_FromDouble(self->eul[count]));
PyTuple_SET_ITEM(tuple, count - begin, PyFloat_FromDouble(self->eul[count]));
}
return list;
return tuple;
}
//----------------------------object[z:y]------------------------
//sequence slice (set)