diff options
author | Maxime Curioni <maxime.curioni@gmail.com> | 2008-07-18 08:59:07 +0400 |
---|---|---|
committer | Maxime Curioni <maxime.curioni@gmail.com> | 2008-07-18 08:59:07 +0400 |
commit | 21674d2db2dbc932fa87699768c1ebb2f61bc941 (patch) | |
tree | 5c20adaf7165b31ff95e18cf5e1b1adaaab31693 /source/blender/freestyle/intern/view_map/ViewMap.h | |
parent | d3973dac717da1557a9a8d50f5c13e25ae75eaa8 (diff) |
soc-2008-mxcurioni: canvas for UnaryFunction0D, UnaryFunction1D, UnaryPredicate0D, UnaryPredicate1D.
UnaryFunction0D and UnaryFunction1D implementations are going to be really challenging due to the changes in the infrastructure: UnaryFunction0D<T> and UnaryFunction0D<T> are templates and must be determined for compile-time. The easiest solution is to support each type individually; unfortunately, it removes the benefit of using an interface. To find a middle ground, a general unary function Python object type was created for 0D and 1D. In both cases, the types have a void* pointer keeping the address of the current unary function type. I am not sure yet if it will work.
Interface0DIterator being removed by a list type, the t() and u() coordinate functions will to be transferred somehow, probably directly at the Interface0D level.
Diffstat (limited to 'source/blender/freestyle/intern/view_map/ViewMap.h')
0 files changed, 0 insertions, 0 deletions