|
Notes |
|
|
(0020454)
|
|
David Gobbi
|
|
2010-04-27 19:57
|
|
Several steps must be taken to achieve this:
1) obviously the relevant bits of the headers must have the BTX/ETX removed
2) the wrappers must be made able to take vtkSomething parameter types names that aren't derived from vtkObjectBase without choking
3) the individual wrappers must be modified to check for and deal with vtkVariant
We don't want to add another "type" to vtkParse.l if it can be avoided. Instead, we just want to pass the name "vtkVariant" to the wrappers as 0x9 and have the wrappers recognize that, because it has no superclass, it must be dealt with differently from vtkObjectBase derived types. |
|
|
|
(0021395)
|
|
David Gobbi
|
|
2010-07-14 22:43
|
|
|
This feature has been added for Python as of June 18, 2010. For Python, the fix was to wrap vtkVariant as its own python type. The issue must be resolved separately for Tcl and Java. |
|
|
|
(0037068)
|
|
Kitware Robot
|
|
2016-08-12 09:55
|
|
Resolving issue as `moved`.
This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
|