archive/blender-archive
Archived
1
1
Fork 0
Code Pull Requests Packages Activity
This repository has been archived on 2023-10-09. You can view files and clone it, but cannot push or open issues or pull requests.
Files
1c5302e68b47c03fd60ab5edefb4a16d6294b7a7
blender-archive/source/blender/python/api2_2x/Curve.c

1209 lines
36 KiB
C
Raw Normal View History

* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*
*
* ***** BEGIN GPL/BL DUAL LICENSE BLOCK *****
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version 2
* of the License, or (at your option) any later version. The Blender
* Foundation also sells licenses for use in proprietary software under
* the Blender License. See http://www.blender.org/BL/ for information
* about this.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software Foundation,
* Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
*
* The Original Code is Copyright (C) 2001-2002 by NaN Holding BV.
* All rights reserved.
*
* This is a new part of Blender.
*
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
* Contributor(s): Jacques Guignot, Stephen Swaney
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
*
* ***** END GPL/BL DUAL LICENSE BLOCK *****
*/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
#include <Python.h>
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
#include "Curve.h"
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
#include <stdio.h>
#include <BLI_arithb.h>
#include <BLI_blenlib.h>
#include <BKE_main.h>
#include <BKE_global.h>
#include <BKE_object.h>
#include <BKE_library.h>
#include <BKE_curve.h>
#include "gen_utils.h"
/*****************************************************************************/
/* The following string definitions are used for documentation strings. */
/* In Python these will be written to the console when doing a */
/* Blender.Curve.__doc__ */
/*****************************************************************************/
char M_Curve_doc[] = "The Blender Curve module\n\n\
This module provides access to **Curve Data** in Blender.\n\
Functions :\n\
New(opt name) : creates a new curve object with the given name (optional)\n\
Get(name) : retreives a curve with the given name (mandatory)\n\
get(name) : same as Get. Kept for compatibility reasons";
char M_Curve_New_doc[] = "";
char M_Curve_Get_doc[] = "xxx";
/*****************************************************************************/
/* Python API function prototypes for the Curve module. */
/*****************************************************************************/
static PyObject *M_Curve_New (PyObject * self, PyObject * args);
static PyObject *M_Curve_Get (PyObject * self, PyObject * args);
/*****************************************************************************/
/* Python BPy_Curve instance methods declarations: */
/*****************************************************************************/
static PyObject *Curve_getName (BPy_Curve * self);
static PyObject *Curve_setName (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getPathLen (BPy_Curve * self);
static PyObject *Curve_setPathLen (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getTotcol (BPy_Curve * self);
static PyObject *Curve_setTotcol (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getMode (BPy_Curve * self);
static PyObject *Curve_setMode (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getBevresol (BPy_Curve * self);
static PyObject *Curve_setBevresol (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getResolu (BPy_Curve * self);
static PyObject *Curve_setResolu (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getResolv (BPy_Curve * self);
static PyObject *Curve_setResolv (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getWidth (BPy_Curve * self);
static PyObject *Curve_setWidth (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getExt1 (BPy_Curve * self);
static PyObject *Curve_setExt1 (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getExt2 (BPy_Curve * self);
static PyObject *Curve_setExt2 (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getControlPoint (BPy_Curve * self, PyObject * args);
static PyObject *Curve_setControlPoint (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getLoc (BPy_Curve * self);
static PyObject *Curve_setLoc (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getRot (BPy_Curve * self);
static PyObject *Curve_setRot (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getSize (BPy_Curve * self);
static PyObject *Curve_setSize (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getNumCurves (BPy_Curve * self);
static PyObject *Curve_isNurb (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getNumPoints (BPy_Curve * self, PyObject * args);
static PyObject *Curve_getNumPoints (BPy_Curve * self, PyObject * args);
/*****************************************************************************/
/* Python method definitions for Blender.Curve module: */
/*****************************************************************************/
struct PyMethodDef M_Curve_methods[] = {
{"New", (PyCFunction) M_Curve_New, METH_VARARGS, M_Curve_New_doc},
{"Get", M_Curve_Get, METH_VARARGS, M_Curve_Get_doc},
{"get", M_Curve_Get, METH_VARARGS, M_Curve_Get_doc},
{NULL, NULL, 0, NULL}
};
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
/*****************************************************************************/
/* Python BPy_Curve instance methods table: */
/*****************************************************************************/
static PyMethodDef BPy_Curve_methods[] = {
{"getName", (PyCFunction) Curve_getName,
METH_NOARGS, "() - Return Curve Data name"},
{"setName", (PyCFunction) Curve_setName,
METH_VARARGS, "() - Sets Curve Data name"},
{"getPathLen", (PyCFunction) Curve_getPathLen,
METH_NOARGS, "() - Return Curve path length"},
{"setPathLen", (PyCFunction) Curve_setPathLen,
METH_VARARGS, "(int) - Sets Curve path length"},
{"getTotcol", (PyCFunction) Curve_getTotcol,
METH_NOARGS, "() - Return the number of materials of the curve"},
{"setTotcol", (PyCFunction) Curve_setTotcol,
METH_VARARGS, "(int) - Sets the number of materials of the curve"},
{"getFlag", (PyCFunction) Curve_getMode,
METH_NOARGS, "() - Return flag (see the doc for semantic)"},
{"setFlag", (PyCFunction) Curve_setMode,
METH_VARARGS, "(int) - Sets flag (see the doc for semantic)"},
{"getBevresol", (PyCFunction) Curve_getBevresol,
METH_NOARGS, "() - Return bevel resolution"},
{"setBevresol", (PyCFunction) Curve_setBevresol,
METH_VARARGS, "(int) - Sets bevel resolution"},
{"getResolu", (PyCFunction) Curve_getResolu,
METH_NOARGS, "() - Return U resolution"},
{"setResolu", (PyCFunction) Curve_setResolu,
METH_VARARGS, "(int) - Sets U resolution"},
{"getResolv", (PyCFunction) Curve_getResolv,
METH_NOARGS, "() - Return V resolution"},
{"setResolv", (PyCFunction) Curve_setResolv,
METH_VARARGS, "(int) - Sets V resolution"},
{"getWidth", (PyCFunction) Curve_getWidth,
METH_NOARGS, "() - Return curve width"},
{"setWidth", (PyCFunction) Curve_setWidth,
METH_VARARGS, "(int) - Sets curve width"},
{"getExt1", (PyCFunction) Curve_getExt1,
METH_NOARGS, "() - Returns extent 1 of the bevel"},
{"setExt1", (PyCFunction) Curve_setExt1,
METH_VARARGS, "(int) - Sets extent 1 of the bevel"},
{"getExt2", (PyCFunction) Curve_getExt2,
METH_NOARGS, "() - Return extent 2 of the bevel "},
{"setExt2", (PyCFunction) Curve_setExt2,
METH_VARARGS, "(int) - Sets extent 2 of the bevel "},
{"getControlPoint", (PyCFunction) Curve_getControlPoint,
METH_VARARGS, "(int numcurve,int numpoint) -\
Gets a control point.Depending upon the curve type, returne a list of 4 or 9 floats"},
{"setControlPoint", (PyCFunction) Curve_setControlPoint,
METH_VARARGS, "(int numcurve,int numpoint,float x,float y,float z,\
float w)(nurbs) or (int numcurve,int numpoint,float x1,...,x9(bezier)\
Sets a control point "},
{"getLoc", (PyCFunction) Curve_getLoc,
METH_NOARGS, "() - Gets Location of the curve (a 3-tuple) "},
{"setLoc", (PyCFunction) Curve_setLoc,
METH_VARARGS, "(3-tuple) - Sets Location "},
{"getRot", (PyCFunction) Curve_getRot,
METH_NOARGS, "() - Gets curve rotation"},
{"setRot", (PyCFunction) Curve_setRot,
METH_VARARGS, "(3-tuple) - Sets curve rotation"},
{"getSize", (PyCFunction) Curve_getSize,
METH_NOARGS, "() - Gets curve size"},
{"setSize", (PyCFunction) Curve_setSize,
METH_VARARGS, "(3-tuple) - Sets curve size"},
bugfix #1345. Curve.isNurb() segfault fixed.
2004-06-03 16:23:51 +00:00
{"getNumCurves", ( PyCFunction ) Curve_getNumCurves,
METH_NOARGS, "() - Gets number of curves in Curve"},
{"isNurb", ( PyCFunction ) Curve_isNurb,
METH_VARARGS, "(nothing or integer) - returns 1 if curve is type Nurb, O otherwise."},
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
{"getNumPoints", (PyCFunction) Curve_getNumPoints,
METH_VARARGS,
"(nothing or integer) - returns the number of points of the specified curve"},
{NULL, NULL, 0, NULL}
};
/*****************************************************************************/
/* Python Curve_Type callback function prototypes: */
/*****************************************************************************/
static void CurveDeAlloc (BPy_Curve * msh);
/* static int CurvePrint (BPy_Curve *msh, FILE *fp, int flags); */
static int CurveSetAttr (BPy_Curve * msh, char *name, PyObject * v);
static PyObject *CurveGetAttr (BPy_Curve * msh, char *name);
static PyObject *CurveRepr (BPy_Curve * msh);
PyObject *Curve_CreatePyObject (struct Curve *curve);
int Curve_CheckPyObject (PyObject * py_obj);
struct Curve *Curve_FromPyObject (PyObject * py_obj);
/*****************************************************************************/
/* Python Curve_Type structure definition: */
/*****************************************************************************/
PyTypeObject Curve_Type = {
PyObject_HEAD_INIT (NULL) /* required macro */
0, /* ob_size */
"Curve", /* tp_name - for printing */
sizeof (BPy_Curve), /* tp_basicsize - for allocation */
0, /* tp_itemsize - for allocation */
/* methods for standard operations */
(destructor) CurveDeAlloc, /* tp_dealloc */
0, /* tp_print */
(getattrfunc) CurveGetAttr, /* tp_getattr */
(setattrfunc) CurveSetAttr, /* tp_setattr */
0, /* tp_compare */
(reprfunc) CurveRepr, /* tp_repr */
/* methods for standard classes */
0, /* tp_as_number */
0, /* tp_as_sequence */
0, /* tp_as_mapping */
0, /* tp_as_hash */
0, /* tp_call */
0, /* tp_str */
0, /* tp_getattro */
0, /* tp_setattro */
0, /* tp_as_buffer */
/* Flags to define presence of optional/expaned features */
0, /* tp_flags */
0, /* tp_doc - documentation string */
0, /* tp_traverse */
/* delete references to contained objects */
0, /* tp_clear */
0, /* tp_richcompare - rich comparisions */
0, /* tp_weaklistoffset - weak reference enabler */
/* new release 2.2 stuff - Iterators */
0, /* tp_iter */
0, /* tp_iternext */
/* Attribute descriptor and subclassing stuff */
BPy_Curve_methods, /* tp_methods */
0, /* tp_members */
0, /* tp_getset; */
0, /* tp_base; */
0, /* tp_dict; */
0, /* tp_descr_get; */
0, /* tp_descr_set; */
0, /* tp_dictoffset; */
0, /* tp_init; */
0, /* tp_alloc; */
0, /* tp_new; */
0, /* tp_free; Low-level free-memory routine */
0, /* tp_is_gc */
0, /* tp_bases; */
0, /* tp_mro; method resolution order */
0, /* tp_defined; */
0, /* tp_weakllst */
0,
};
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*****************************************************************************/
/* Function: M_Curve_New */
/* Python equivalent: Blender.Curve.New */
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
M_Curve_New (PyObject * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
char buf[24];
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
char *name = NULL;
BPy_Curve *pycurve; /* for Curve Data object wrapper in Python */
Curve *blcurve = 0; /* for actual Curve Data we create in Blender */
if (!PyArg_ParseTuple (args, "|s", &name))
fixed the bug Joseph Gilbert found in numerous python files. newly created data objs had incorrect user counts.
2003-11-11 10:13:04 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected string argument or no argument"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
blcurve = add_curve (OB_CURVE); /* first create the Curve Data in Blender */
if (blcurve == NULL) /* bail out if add_curve() failed */
fixed the bug Joseph Gilbert found in numerous python files. newly created data objs had incorrect user counts.
2003-11-11 10:13:04 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
"couldn't create Curve Data in Blender"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
fixed the bug Joseph Gilbert found in numerous python files. newly created data objs had incorrect user counts.
2003-11-11 10:13:04 +00:00
/* return user count to zero because add_curve() inc'd it */
blcurve->id.us = 0;
/* create python wrapper obj */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
pycurve = (BPy_Curve *) PyObject_NEW (BPy_Curve, &Curve_Type);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
if (pycurve == NULL)
fixed the bug Joseph Gilbert found in numerous python files. newly created data objs had incorrect user counts.
2003-11-11 10:13:04 +00:00
return (EXPP_ReturnPyObjError (PyExc_MemoryError,
"couldn't create Curve Data object"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
pycurve->curve = blcurve; /* link Python curve wrapper to Blender Curve */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
if (name)
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyOS_snprintf (buf, sizeof (buf), "%s", name);
rename_id (&blcurve->id, buf);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (PyObject *) pycurve;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
/*****************************************************************************/
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
/* Function: M_Curve_Get */
/* Python equivalent: Blender.Curve.Get */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
M_Curve_Get (PyObject * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
char *name = NULL;
Curve *curv_iter;
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
BPy_Curve *wanted_curv;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "|s", &name)) /* expects nothing or a string */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"expected string argument"));
if (name)
{ /*a name has been given */
/* Use the name to search for the curve requested */
wanted_curv = NULL;
curv_iter = G.main->curve.first;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
while ((curv_iter) && (wanted_curv == NULL))
{
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (strcmp (name, curv_iter->id.name + 2) == 0)
{
wanted_curv =
(BPy_Curve *) PyObject_NEW (BPy_Curve, &Curve_Type);
if (wanted_curv)
wanted_curv->curve = curv_iter;
}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
curv_iter = curv_iter->id.next;
}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (wanted_curv == NULL)
{ /* Requested curve doesn't exist */
char error_msg[64];
PyOS_snprintf (error_msg, sizeof (error_msg),
"Curve \"%s\" not found", name);
return (EXPP_ReturnPyObjError (PyExc_NameError, error_msg));
}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (PyObject *) wanted_curv;
} /* end of if(name) */
else
{
/* no name has been given; return a list of all curves by name. */
PyObject *curvlist;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
curv_iter = G.main->curve.first;
curvlist = PyList_New (0);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (curvlist == NULL)
Replace deprecated methods from old api: PythonReturnErrorObject PythonIncRef Fix some compiler warnings about missing initializers in method tables.
2004-06-06 22:42:51 +00:00
return (EXPP_ReturnPyObjError (PyExc_MemoryError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't create PyList"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
while (curv_iter)
{
BPy_Curve *found_cur =
(BPy_Curve *) PyObject_NEW (BPy_Curve, &Curve_Type);
found_cur->curve = curv_iter;
PyList_Append (curvlist, (PyObject *) found_cur);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
curv_iter = curv_iter->id.next;
}
return (curvlist);
} /* end of else */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
/*****************************************************************************/
- More renaming all around to follow our conventions - Implemented partially Blender.Sys - Worked on issues related to sys, path - Took away most "debug" printfs
2003-06-28 07:38:21 +00:00
/* Function: Curve_Init */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *
Curve_Init (void)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *submodule;
* Fix compilation errors on Windows hopefully. Implemented the suggestion done by Aphex - thanks. * Added the doc strings to the Object module. * Added more functionality to the Object module.
2003-06-02 20:15:50 +00:00
Curve_Type.ob_type = &PyType_Type;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
submodule = Py_InitModule3 ("Blender.Curve", M_Curve_methods, M_Curve_doc);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (submodule);
}
/*****************************************************************************/
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
/* Python BPy_Curve methods: */
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
/* gives access to */
/* name, pathlen totcol flag bevresol */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
/* resolu resolv width ext1 ext2 */
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
/* controlpoint loc rot size */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* numpts */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*****************************************************************************/
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getName (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyString_FromString (self->curve->id.name + 2);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.name attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setName (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
char *name;
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
char buf[50];
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "s", &(name)))
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"expected string argument"));
PyOS_snprintf (buf, sizeof (buf), "%s", name);
rename_id (&self->curve->id, buf); /* proper way in Blender */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getPathLen (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->pathlen);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.pathlen attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setPathLen (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->pathlen)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getTotcol (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->totcol);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.totcol attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setTotcol (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->totcol)))
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getMode (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->flag);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.flag attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setMode (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->flag)))
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getBevresol (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->bevresol);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.bevresol attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setBevresol (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->bevresol)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getResolu (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->resolu);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.resolu attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setResolu (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->resolu)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getResolv (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyInt_FromLong ((long) self->curve->resolv);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.resolv attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setResolv (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "i", &(self->curve->resolv)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getWidth (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyFloat_FromDouble ((double) self->curve->width);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.width attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setWidth (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "f", &(self->curve->width)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected float argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getExt1 (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyFloat_FromDouble ((double) self->curve->ext1);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.ext1 attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setExt1 (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "f", &(self->curve->ext1)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected float argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getExt2 (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *attr = PyFloat_FromDouble ((double) self->curve->ext2);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr)
return attr;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't get Curve.ext2 attribute"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setExt2 (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "f", &(self->curve->ext2)))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected float argument"));
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
/*
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
static PyObject *Curve_setControlPoint(BPy_Curve *self, PyObject *args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
Nurb*ptrnurb = self->curve->nurb.first;
int numcourbe,numpoint,i,j;
float x,y,z,w;
float bez[9];
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
if (!ptrnurb){ Py_INCREF(Py_None);return Py_None;}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
if (ptrnurb->bp)
if (!PyArg_ParseTuple(args, "iiffff", &numcourbe,&numpoint,&x,&y,&z,&w))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
several bug fixes
2003-06-21 20:44:44 +00:00
"expected int int float float float float arguments"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
if (ptrnurb->bezt)
if (!PyArg_ParseTuple(args, "iifffffffff", &numcourbe,&numpoint,
several bug fixes
2003-06-21 20:44:44 +00:00
bez,bez+1,bez+2,bez+3,bez+4,bez+5,bez+6,bez+7,bez+8))
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
several bug fixes
2003-06-21 20:44:44 +00:00
"expected int int float float float float float float "
"float float float arguments"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
for(i = 0;i< numcourbe;i++)
ptrnurb=ptrnurb->next;
if (ptrnurb->bp)
{
ptrnurb->bp[numpoint].vec[0] = x;
ptrnurb->bp[numpoint].vec[1] = y;
ptrnurb->bp[numpoint].vec[2] = z;
ptrnurb->bp[numpoint].vec[3] = w;
}
if (ptrnurb->bezt)
{
for(i = 0;i<3;i++)
several bug fixes
2003-06-21 20:44:44 +00:00
for(j = 0;j<3;j++)
ptrnurb->bezt[numpoint].vec[i][j] = bez[i*3+j];
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
several bug fixes
2003-06-21 20:44:44 +00:00
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
Py_INCREF(Py_None);
return Py_None;
}
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
*/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setControlPoint (BPy_Curve * self, PyObject * args)
{
PyObject *listargs = 0;
Nurb *ptrnurb = self->curve->nurb.first;
int numcourbe, numpoint, i, j;
if (!ptrnurb)
{
Py_INCREF (Py_None);
return Py_None;
}
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
if (ptrnurb->bp)
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "iiO", &numcourbe, &numpoint, &listargs))
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"expected int int list arguments"));
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
if (ptrnurb->bezt)
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "iiO", &numcourbe, &numpoint, &listargs))
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"expected int int list arguments"));
for (i = 0; i < numcourbe; i++)
ptrnurb = ptrnurb->next;
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
if (ptrnurb->bp)
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < 4; i++)
ptrnurb->bp[numpoint].vec[i] =
PyFloat_AsDouble (PyList_GetItem (listargs, i));
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
if (ptrnurb->bezt)
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < 3; i++)
for (j = 0; j < 3; j++)
ptrnurb->bezt[numpoint].vec[i][j] =
PyFloat_AsDouble (PyList_GetItem (listargs, i * 3 + j));
Py_INCREF (Py_None);
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
return Py_None;
}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getControlPoint (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *liste = PyList_New (0); /* return values */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Nurb *ptrnurb;
int i, j;
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* input args: requested curve and point number on curve */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
int numcourbe, numpoint;
if (!PyArg_ParseTuple (args, "ii", &numcourbe, &numpoint))
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
"expected int int arguments"));
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if ((numcourbe < 0) || (numpoint < 0))
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
" arguments must be non-negative"));
/* if no nurbs in this curve obj */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!self->curve->nurb.first)
return liste;
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* walk the list of nurbs to find requested numcourbe */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
ptrnurb = self->curve->nurb.first;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < numcourbe; i++)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
ptrnurb = ptrnurb->next;
if (!ptrnurb) /* if zero, we ran just ran out of curves */
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"curve index out of range"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* check numpoint param against pntsu */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (numpoint >= ptrnurb->pntsu)
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"point index out of range"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (ptrnurb->bp) /* if we are a nurb curve, you get 4 values */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < 4; i++)
PyList_Append (liste,
PyFloat_FromDouble (ptrnurb->bp[numpoint].vec[i]));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (ptrnurb->bezt) /* if we are a bezier, you get 9 values */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < 3; i++)
for (j = 0; j < 3; j++)
PyList_Append (liste,
PyFloat_FromDouble (ptrnurb->bezt[numpoint].
vec[i][j]));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
return liste;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getLoc (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
int i;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *liste = PyList_New (3);
for (i = 0; i < 3; i++)
PyList_SetItem (liste, i, PyFloat_FromDouble (self->curve->loc[i]));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return liste;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setLoc (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *listargs = 0;
int i;
if (!PyArg_ParseTuple (args, "O", &listargs))
return EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected list argument");
if (!PyList_Check (listargs))
return (EXPP_ReturnPyObjError (PyExc_TypeError, "expected a list"));
for (i = 0; i < 3; i++)
{
PyObject *xx = PyList_GetItem (listargs, i);
self->curve->loc[i] = PyFloat_AsDouble (xx);
}
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getRot (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
int i;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *liste = PyList_New (3);
for (i = 0; i < 3; i++)
PyList_SetItem (liste, i, PyFloat_FromDouble (self->curve->rot[i]));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return liste;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setRot (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *listargs = 0;
int i;
if (!PyArg_ParseTuple (args, "O", &listargs))
return EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected list argument");
if (!PyList_Check (listargs))
return (EXPP_ReturnPyObjError (PyExc_TypeError, "expected a list"));
for (i = 0; i < 3; i++)
{
PyObject *xx = PyList_GetItem (listargs, i);
self->curve->rot[i] = PyFloat_AsDouble (xx);
}
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getSize (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
int i;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *liste = PyList_New (3);
for (i = 0; i < 3; i++)
PyList_SetItem (liste, i, PyFloat_FromDouble (self->curve->size[i]));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return liste;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_setSize (BPy_Curve * self, PyObject * args)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *listargs = 0;
int i;
if (!PyArg_ParseTuple (args, "O", &listargs))
return EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected list argument");
if (!PyList_Check (listargs))
return (EXPP_ReturnPyObjError (PyExc_TypeError, "expected a list"));
for (i = 0; i < 3; i++)
{
PyObject *xx = PyList_GetItem (listargs, i);
self->curve->size[i] = PyFloat_AsDouble (xx);
}
Py_INCREF (Py_None);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
return Py_None;
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/*
* Count the number of splines in a Curve Object
* int getNumCurves()
*/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getNumCurves (BPy_Curve * self)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
Nurb *ptrnurb;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *ret_val;
int num_curves = 0; /* start with no splines */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* get curve */
ptrnurb = self->curve->nurb.first;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (ptrnurb) /* we have some nurbs in this curve */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
while (1)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
++num_curves;
ptrnurb = ptrnurb->next;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!ptrnurb) /* no more curves */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
break;
}
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
ret_val = PyInt_FromLong ((long) num_curves);
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (ret_val)
return ret_val;
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* oops! */
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
"couldn't get number of curves"));
}
/*
* count the number of points in a give spline
* int getNumPoints( curve_num=0 )
*
*/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_getNumPoints (BPy_Curve * self, PyObject * args)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
Nurb *ptrnurb;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *ret_val;
int curve_num = 0; /* default spline number */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
int i;
/* parse input arg */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "|i", &curve_num))
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* check arg - must be non-negative */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (curve_num < 0)
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"argument must be non-negative"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* walk the list of curves looking for our curve */
ptrnurb = self->curve->nurb.first;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!ptrnurb) /* no splines in this Curve */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"no splines in this Curve"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < curve_num; i++)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
ptrnurb = ptrnurb->next;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!ptrnurb) /* if zero, we ran just ran out of curves */
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"curve index out of range"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* pntsu is the number of points in curve */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
ret_val = PyInt_FromLong ((long) ptrnurb->pntsu);
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (ret_val)
return ret_val;
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* oops! */
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
"couldn't get number of points for curve"));
}
/*
* Test whether a given spline of a Curve is a nurb
* as opposed to a bezier
* int isNurb( curve_num=0 )
*/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
Curve_isNurb (BPy_Curve * self, PyObject * args)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
int curve_num = 0; /* default value */
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
int is_nurb;
Nurb *ptrnurb;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *ret_val;
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
int i;
/* parse and check input args */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!PyArg_ParseTuple (args, "|i", &curve_num))
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"expected int argument"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (curve_num < 0)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
"curve number must be non-negative"));
}
ptrnurb = self->curve->nurb.first;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!ptrnurb) /* no splines in this curve */
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"no splines in this Curve"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
for (i = 0; i < curve_num; i++)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
{
ptrnurb = ptrnurb->next;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (!ptrnurb) /* if zero, we ran just ran out of curves */
return (EXPP_ReturnPyObjError (PyExc_AttributeError,
"curve index out of range"));
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
/* right now, there are only two curve types, nurb and bezier. */
is_nurb = ptrnurb->bp ? 1 : 0;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
ret_val = PyInt_FromLong ((long) is_nurb);
if (ret_val)
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
return ret_val;
/* oops */
return (EXPP_ReturnPyObjError (PyExc_RuntimeError,
"couldn't get curve type"));
}
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/*****************************************************************************/
/* Function: CurveDeAlloc */
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
/* Description: This is a callback function for the BPy_Curve type. It is */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/* the destructor function. */
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static void
CurveDeAlloc (BPy_Curve * self)
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
PyObject_DEL (self);
}
/*****************************************************************************/
/* Function: CurveGetAttr */
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
/* Description: This is a callback function for the BPy_Curve type. It is */
/* the function that accesses BPy_Curve "member variables" and */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/* methods. */
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
CurveGetAttr (BPy_Curve * self, char *name) /* getattr */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
PyObject *attr = Py_None;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (strcmp (name, "name") == 0)
attr = PyString_FromString (self->curve->id.name + 2);
if (strcmp (name, "pathlen") == 0)
attr = PyInt_FromLong (self->curve->pathlen);
if (strcmp (name, "totcol") == 0)
attr = PyInt_FromLong (self->curve->totcol);
if (strcmp (name, "flag") == 0)
attr = PyInt_FromLong (self->curve->flag);
if (strcmp (name, "bevresol") == 0)
attr = PyInt_FromLong (self->curve->bevresol);
if (strcmp (name, "resolu") == 0)
attr = PyInt_FromLong (self->curve->resolu);
if (strcmp (name, "resolv") == 0)
attr = PyInt_FromLong (self->curve->resolv);
if (strcmp (name, "width") == 0)
attr = PyFloat_FromDouble (self->curve->width);
if (strcmp (name, "ext1") == 0)
attr = PyFloat_FromDouble (self->curve->ext1);
if (strcmp (name, "ext2") == 0)
attr = PyFloat_FromDouble (self->curve->ext2);
if (strcmp (name, "loc") == 0)
return Curve_getLoc (self);
if (strcmp (name, "rot") == 0)
return Curve_getRot (self);
if (strcmp (name, "size") == 0)
return Curve_getSize (self);
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
#if 0
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (strcmp (name, "numpts") == 0)
return Curve_getNumPoints (self);
Modification of the GetControlPoint function by Stephen, who is now responsible for this module slight bug fixes (Steph.)
2003-09-02 20:11:11 +00:00
#endif
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
if (!attr)
return (EXPP_ReturnPyObjError (PyExc_MemoryError,
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
"couldn't create PyObject"));
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (attr != Py_None)
return attr; /* member attribute found, return it */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/* not an attribute, search the methods table */
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return Py_FindMethod (BPy_Curve_methods, (PyObject *) self, name);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
/*****************************************************************************/
/* Function: CurveSetAttr */
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
/* Description: This is a callback function for the BPy_Curve type. It is the */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/* function that sets Curve Data attributes (member variables). */
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static int
CurveSetAttr (BPy_Curve * self, char *name, PyObject * value)
{
PyObject *valtuple;
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
PyObject *error = NULL;
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
valtuple = Py_BuildValue ("(O)", value);
/* resolu resolv width ext1 ext2 */
if (!valtuple)
return EXPP_ReturnIntError (PyExc_MemoryError,
"CurveSetAttr: couldn't create PyTuple");
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
if (strcmp (name, "name") == 0)
error = Curve_setName (self, valtuple);
else if (strcmp (name, "pathlen") == 0)
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
error = Curve_setPathLen (self, valtuple);
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
else if (strcmp (name, "resolu") == 0)
error = Curve_setResolu (self, valtuple);
else if (strcmp (name, "resolv") == 0)
error = Curve_setResolv (self, valtuple);
else if (strcmp (name, "width") == 0)
error = Curve_setWidth (self, valtuple);
else if (strcmp (name, "ext1") == 0)
error = Curve_setExt1 (self, valtuple);
else if (strcmp (name, "ext2") == 0)
error = Curve_setExt2 (self, valtuple);
change the values of the functions get/set size/loc/rot to lists. added the attributes loc, rot, size changed the parameters of getControlPoint to int int list cosmetic changes in names
2003-07-09 21:18:34 +00:00
else if (strcmp (name, "loc") == 0)
error = Curve_setLoc (self, valtuple);
else if (strcmp (name, "rot") == 0)
error = Curve_setRot (self, valtuple);
else if (strcmp (name, "size") == 0)
error = Curve_setSize (self, valtuple);
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
else
{ /* Error */
Py_DECREF (valtuple);
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if ((strcmp (name, "Types") == 0) || (strcmp (name, "Modes") == 0))
return (EXPP_ReturnIntError (PyExc_AttributeError,
"constant dictionary -- cannot be changed"));
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
else
return (EXPP_ReturnIntError (PyExc_KeyError, "attribute not found"));
}
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
Py_DECREF (valtuple);
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (error != Py_None)
return -1;
Py_DECREF (Py_None);
return 0;
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
/*****************************************************************************/
/* Function: CurveRepr */
some cleanup; naming conventions
2003-06-27 07:35:55 +00:00
/* Description: This is a callback function for the BPy_Curve type. It */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
/* builds a meaninful string to represent curve objects. */
/*****************************************************************************/
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
static PyObject *
CurveRepr (BPy_Curve * self) /* used by 'repr' */
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return PyString_FromFormat ("[Curve \"%s\"]", self->curve->id.name + 2);
* Added Blender.Curve submodule, written by Jacques Guignot (guignot): Jacques contributed a new module to exppython, one that isn't available in the current 2.27 API. Welcome, guignot : ).
2003-05-17 07:08:08 +00:00
}
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
PyObject *
Curve_CreatePyObject (struct Curve * curve)
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
BPy_Curve *blen_object;
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
blen_object = (BPy_Curve *) PyObject_NEW (BPy_Curve, &Curve_Type);
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
if (blen_object == NULL)
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (NULL);
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
blen_object->curve = curve;
return ((PyObject *) blen_object);
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
}
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
int
Curve_CheckPyObject (PyObject * py_obj)
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
return (py_obj->ob_type == &Curve_Type);
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
}
* Module Curve updated: Jacques Guignot (guignot) sent updated files for his Curve module. * Module Armature (and its submodule Bone) added: Jordi Rovira i Bonet (bandoler) contributed both modules, which are NEW additions to Blender Python, not available in Blender 2.27. * Added function to NMesh.c: Jordi again. He added the function NMesh_getVertexInfluence().
2003-05-29 04:00:35 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
struct Curve *
Curve_FromPyObject (PyObject * py_obj)
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
{
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
BPy_Curve *blen_obj;
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
General housekeeping and cleanup. Move static declarations and data definitions from .h files into corresponding .c files. Blame zr for this since he's the one who pointed out that our bpy headers were a mish-mash of stuff that belonged in the .c files! In a nutshell, the headers should contain the declarations necessary to use a module or class. The implementation files ( .c in this case ) should contain statements that allocate storage ( definitions in the C sense ) and executable code. When used at file scope, the keyword 'static' means "don't tell anyone else about this". Since headers describe a public interface, static declarations and definitions belong in the implementation files. The net result of all this is that after stuff has moved out into the .c files, the .h files are empty or mostly empty. I didn't delete them since there seem to be some public declarations and because I did not want to cause too much disruption at one time. Time enough for that later!
2004-03-29 08:16:18 +00:00
blen_obj = (BPy_Curve *) py_obj;
return (blen_obj->curve);
Guignot implemented 3 functions needed by the Object Module
2003-05-20 03:53:30 +00:00
}
Copy Permalink