This new release wraps VTK 5.0.1, recently released by Kitware. It also includes a number of changes in the wrapper code, the most important of which is a fix for widget problems.
The release notes on the file download page have the list of fixes, but I would like to add some details.
vtkMy and vtkLocal won't work. I submitted a bug Kitware to ask for a small fix to a class that would allow me to simplify the wrapper code so that vtkMy and vtkLocal will work.
I have not compiled for 64 bit vtkIdType, nor have I made an x64 build. Both should be very possible, but the data types in vtkWrapDotNet.cxx might need to be corrected.
I have been told that the control can crash in the Visual Studio designer. I think it may happen when another control overlaps the VTK control, but I've only noticed it once. The way to debug that is to start a debugging session for the control and specify devenv.exe as the application to debug. I haven't tried it yet.
I'm thinking about making the native and managed dlls into assemblies so they are properly versioned. This would solve problems of having multiple VTK copies on the same machine and would, I think, be prerequisite for signing the Dlls in order to use them in web services. Executing native code from a managed Dll requires permissions granted only to signed assemblies. Assemblies are more painful to develop but easier to deploy, so I'm open to suggestions.
I'm grateful for the suggestions people have sent me. I hope the new release works well.
Drew
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This new release wraps VTK 5.0.1, recently released by Kitware. It also includes a number of changes in the wrapper code, the most important of which is a fix for widget problems.
The release notes on the file download page have the list of fixes, but I would like to add some details.
vtkMy and vtkLocal won't work. I submitted a bug Kitware to ask for a small fix to a class that would allow me to simplify the wrapper code so that vtkMy and vtkLocal will work.
I have not compiled for 64 bit vtkIdType, nor have I made an x64 build. Both should be very possible, but the data types in vtkWrapDotNet.cxx might need to be corrected.
I have been told that the control can crash in the Visual Studio designer. I think it may happen when another control overlaps the VTK control, but I've only noticed it once. The way to debug that is to start a debugging session for the control and specify devenv.exe as the application to debug. I haven't tried it yet.
I'm thinking about making the native and managed dlls into assemblies so they are properly versioned. This would solve problems of having multiple VTK copies on the same machine and would, I think, be prerequisite for signing the Dlls in order to use them in web services. Executing native code from a managed Dll requires permissions granted only to signed assemblies. Assemblies are more painful to develop but easier to deploy, so I'm open to suggestions.
I'm grateful for the suggestions people have sent me. I hope the new release works well.
Drew
Thank you for your hard works.
It's a really good library.
I successfully used it to display some data.
I made some translation of exampe cxx and test cxx files in distribution.
lotus.