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

Freestyle: Python API documentation updates.

Browse Source 
Fixed dead references of API identifiers (e.g., freestyle.types.Interface0D)
due to relocations of the identifiers into submodules.  Also made various minor
revisions of mark-ups and typos.
This commit is contained in:
Tamito Kajiyama
2014-09-19 13:22:20 +09:00
parent 98a78963be
commit 64ade99ecc
101 changed files with 455 additions and 401 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
source/blender/freestyle/intern/python/UnaryFunction0D/UnaryFunction0D_Material/BPy_MaterialF0D.cpp
View File

@@ -35,7 +35,7 @@ extern "C" {
//------------------------INSTANCE METHODS ----------------------------------
static char MaterialF0D___doc__[] =
"Class hierarchy: :class:`UnaryFunction0D` > :class:`UnaryFunction0DMaterial` > :class:`MaterialF0D`\n"
"Class hierarchy: :class:`freestyle.types.UnaryFunction0D` > :class:`freestyle.types.UnaryFunction0DMaterial` > :class:`MaterialF0D`\n"
"\n"
".. method:: __init__()\n"
"\n"
@@ -44,22 +44,22 @@ static char MaterialF0D___doc__[] =
".. method:: __call__(it)\n"
"\n"
" Returns the material of the object evaluated at the\n"
" :class:`Interface0D` pointed by the Interface0DIterator. This\n"
" evaluation can be ambiguous (in the case of a :class:`TVertex` for\n"
" example. This functor tries to remove this ambiguity using the\n"
" context offered by the 1D element to which the Interface0DIterator\n"
" belongs to and by arbitrary choosing the material of the face that\n"
" lies on its left when following the 1D element if there are two\n"
" different materials on each side of the point. However, there\n"
" still can be problematic cases, and the user willing to deal with\n"
" this cases in a specific way should implement its own getMaterial\n"
" functor.\n"
" :class:`freestyle.types.Interface0D` pointed by the\n"
" Interface0DIterator. This evaluation can be ambiguous (in the case of\n"
" a :class:`freestyle.types.TVertex` for example. This functor tries to\n"
" remove this ambiguity using the context offered by the 1D element to\n"
" which the Interface0DIterator belongs to and by arbitrary choosing the\n"
" material of the face that lies on its left when following the 1D\n"
" element if there are two different materials on each side of the\n"
" point. However, there still can be problematic cases, and the user\n"
" willing to deal with this cases in a specific way should implement its\n"
" own getMaterial functor.\n"
"\n"
" :arg it: An Interface0DIterator object.\n"
" :type it: :class:`Interface0DIterator`\n"
" :type it: :class:`freestyle.types.Interface0DIterator`\n"
" :return: The material of the object evaluated at the pointed\n"
" Interface0D.\n"
" :rtype: :class:`Material`\n";
" :rtype: :class:`freestyle.types.Material`\n";
static int MaterialF0D___init__(BPy_MaterialF0D *self, PyObject *args, PyObject *kwds)
{