vtkImageDilateErode3D has a bug in the kernel size input field

[GoogleCodeExporter]

What steps will reproduce the problem?
1. configure the vtkImageDilateErode3D and click OK
2.
3.

What is the expected output? What do you see instead?
The kernel size should work in a format of (x, x, x) or in a certain way.
But you can't input the kernel size in any way I can image in Python.

What version of the product are you using? On what operating system?
8.5.3085

Please provide any additional information below.

Original issue reported on code.google.com by zyz...@gmail.com on 1 Jul 2008 at 8:31

[GoogleCodeExporter]

Thanks for the bug report.

I'll certainly take a look at this.  All the vtk* modules are automatically 
wrapped,
hence the fact that there are some problems.

Have you also tried the imageGreyDilate and imageGreyErode modules?  The 
hand-wrapped
modules are always to be preferred over the automatically wrapped vtk ones.

Original comment by cpbotha on 1 Jul 2008 at 1:42

• Changed state: Accepted
• Added labels: Milestone-Release8.9

[GoogleCodeExporter]

Thanks for the comments. At last I coded an user module to do such task. 

Original comment by zyz...@gmail.com on 1 Jul 2008 at 1:46

[GoogleCodeExporter]

Original comment by cpbotha on 4 Dec 2008 at 1:04

• Added labels: Milestone-Release8.12

[GoogleCodeExporter]

Original comment by cpbotha on 23 Dec 2008 at 5:36

• Added labels: Milestone-Release9.1

[GoogleCodeExporter]

vtkImageExtractComponents (and I guess bunches of other automatically wrapped 
modules
with tuple-taking methods) have the same problem.  Try to configure the 
"SetComponents".

Original comment by cpbotha on 15 Mar 2009 at 1:27

[GoogleCodeExporter]

Original comment by cpbotha on 28 Jul 2009 at 11:59

• Added labels: Milestone-Release9.8
• Removed labels: Milestone-Release9.1

[GoogleCodeExporter]

In VTK 5.4.2, one has to do SetKernelSize(x,y,z), i.e. no tuple but 3 separate 
parameters.  Have to fix ConfigVtkObj to account for this.

Original comment by cpbotha on 10 Aug 2009 at 2:11

[GoogleCodeExporter]

This issue was closed by revision r3771.

Original comment by cpbotha on 10 Aug 2009 at 2:34

• Changed state: Fixed