namespace
{
// Define own interaction style
class myVtkInteractorStyleImage : public vtkInteractorStyleImage
{
public:
static myVtkInteractorStyleImage* New(); //not define
vtkTypeMacro(myVtkInteractorStyleImage, vtkInteractorStyleImage);//not define
...
};
vtkStandardNewMacro(myVtkInteractorStyleImage);//defined!!
} // namespace
```
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 6, 2022, 12:12pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/8 "2022-12-06T12:12:23Z")
So, please, copy and paste the error message as it is here.
---
### Author:  [@a0980543469](https://discourse.vtk.org/u/a0980543469)
#### Post date: [December 6, 2022, 12:57pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/9 "2022-12-06T12:57:14Z")
I used Chineese version, sorry about that.
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 6, 2022, 1:03pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/10 "2022-12-06T13:03:26Z")
That’s the definition of the vtkTypeMacro macro. We need the text of the error message output by the compiler.
---
### Author:  [@a0980543469](https://discourse.vtk.org/u/a0980543469)
#### Post date: [December 7, 2022, 5:37am UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/11 "2022-12-07T05:37:50Z")
Why I said “not define” is base on what I seem the green waveline in this code(now still has), the error message hasn’t show any error now (after I rewrite it).
The earlier code I am sure that I had include the header file `#include `, but I cleared the old one.
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 7, 2022, 1:57pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/12 "2022-12-07T13:57:28Z")
Please, try to compile the program anyway. The compiler will surely issue an error message. Then copy and paste it here.
---
### Author:  [@a0980543469](https://discourse.vtk.org/u/a0980543469)
#### Post date: [December 7, 2022, 2:16pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/13 "2022-12-07T14:16:49Z")
Like this? I can’t get the point
It run correctly and also build a \*.exe
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 7, 2022, 10:38pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/14 "2022-12-07T22:38:16Z")
Yes, that’s one of the many errors. Now it’s necessary to translate the messages to English.
---
### Author:  [@a0980543469](https://discourse.vtk.org/u/a0980543469)
#### Post date: [December 10, 2022, 5:12am UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/15 "2022-12-10T05:12:21Z")
```auto
Error (active) E2512 the argument to a feature-test macro must be a simple identifier
```
maybe is like this
all the error is E2512
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 10, 2022, 12:04pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/16 "2022-12-10T12:04:07Z")
It seems to be an incompatiblity between the Qt version and VS version you are using. In your case, I’d recommend to either:
a) Use Qt Creator IDE to develop your program (VS IDE is bloatware, anyway);
b) Follow this: [Problem with new Visual Studio update 2017 Version 15.8.0 and Qt 5.9.5 | Qt Forum](https://forum.qt.io/topic/93711/problem-with-new-visual-studio-update-2017-version-15-8-0-and-qt-5-9-5/24) .
---
### Author:  [@a0980543469](https://discourse.vtk.org/u/a0980543469)
#### Post date: [December 11, 2022, 9:17am UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/17 "2022-12-11T09:17:00Z")
OKay, thank for your help
Maybe I’ll try another compiler. Because I have no idea to put the VTK library or others into QT creator~ 🤣, I choose to use VS (which used by my class teacher)
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [December 11, 2022, 3:08pm UTC](https://discourse.vtk.org/t/the-problem-in-vtkinteractorstyleimage-to-set-dicom-slice-by-mousewheel/9732/18 "2022-12-11T15:08:36Z")
Hello,
You don’t need to throw away the VS IDE if you don’t feel comfortable. I don’t enjoy much any of Microsoft products, but I support freedom of tool choice. I just suggested using Qt’s IDE because it’ll do the job more efficiently, IMO.
You can still use VS tool chain (its compiler is called `cl.exe`, its Makefile processor is called `nmake` and so on) but you can use a better IDE IMO 🙂.
Adding libraries is not that difficult using alternatives. If you’d like how to setup libraries in `qmake`, you can do something like this in the `.pro` file:
```bash
#========== The VTK include and lib paths and libraries==================
_VTK_INCLUDE = $$(VTK_INCLUDE)
isEmpty(_VTK_INCLUDE){
error(VTK_INCLUDE environment variable not defined.)
}
_VTK_LIB = $$(VTK_LIB)
isEmpty(_VTK_LIB){
error(VTK_LIB environment variable not defined.)
}
_VTK_VERSION_SUFFIX = $$(VTK_VERSION_SUFFIX)
isEmpty(_VTK_VERSION_SUFFIX){
warning(VTK_VERSION_SUFFIX environment variable not defined or empty.)
}
gcc:QMAKE_CXXFLAGS += -isystem $$_VTK_INCLUDE #This is to suppress the countless compiler warnings from VTK headers
clang:QMAKE_CXXFLAGS += -isystem $$_VTK_INCLUDE #This is to suppress the countless compiler warnings from VTK headers
mingw:QMAKE_CXXFLAGS += -isystem $$_VTK_INCLUDE #This is to suppress the countless compiler warnings from VTK headers
msvc:QMAKE_CXXFLAGS += /external:I $$_VTK_INCLUDE #This is to suppress the countless compiler warnings from VTK headers
INCLUDEPATH += $$_VTK_INCLUDE
LIBPATH += $$_VTK_LIB
LIBS += -lvtkGUISupportQt$$_VTK_VERSION_SUFFIX \
-lvtkCommonCore$$_VTK_VERSION_SUFFIX \
-lvtkFiltersSources$$_VTK_VERSION_SUFFIX \
-lvtkRenderingCore$$_VTK_VERSION_SUFFIX \
-lvtkCommonExecutionModel$$_VTK_VERSION_SUFFIX \
-lvtkInteractionStyle$$_VTK_VERSION_SUFFIX \
-lvtkRenderingOpenGL2$$_VTK_VERSION_SUFFIX \
-lvtkRenderingAnnotation$$_VTK_VERSION_SUFFIX \
-lvtkRenderingFreeType$$_VTK_VERSION_SUFFIX \
-lvtkInteractionWidgets$$_VTK_VERSION_SUFFIX \
-lvtkCommonDataModel$$_VTK_VERSION_SUFFIX \
-lvtkFiltersGeneral$$_VTK_VERSION_SUFFIX \
-lvtkCommonTransforms$$_VTK_VERSION_SUFFIX \
-lvtkImagingSources$$_VTK_VERSION_SUFFIX \
-lvtkImagingCore$$_VTK_VERSION_SUFFIX \
-lvtkFiltersCore$$_VTK_VERSION_SUFFIX \
-lvtkFiltersExtraction$$_VTK_VERSION_SUFFIX \
-lvtkImagingFourier$$_VTK_VERSION_SUFFIX \
-lvtkCommonMisc$$_VTK_VERSION_SUFFIX \
-lvtkCommonComputationalGeometry$$_VTK_VERSION_SUFFIX \
-lvtkCommonMath$$_VTK_VERSION_SUFFIX \
-lvtksys$$_VTK_VERSION_SUFFIX \
-lvtkFiltersGeometry$$_VTK_VERSION_SUFFIX \
-lvtkCommonColor$$_VTK_VERSION_SUFFIX \
-lvtkCommonSystem$$_VTK_VERSION_SUFFIX \
-lvtkglew$$_VTK_VERSION_SUFFIX \
-lvtkfreetype$$_VTK_VERSION_SUFFIX \
-lvtkzlib$$_VTK_VERSION_SUFFIX \
-lvtkFiltersHybrid$$_VTK_VERSION_SUFFIX \
-lvtkFiltersModeling$$_VTK_VERSION_SUFFIX \
-lvtkImagingGeneral$$_VTK_VERSION_SUFFIX \
-lvtkRenderingVolume$$_VTK_VERSION_SUFFIX \
-lvtkFiltersStatistics$$_VTK_VERSION_SUFFIX \
-lvtkImagingStencil$$_VTK_VERSION_SUFFIX \
-lvtkImagingHybrid$$_VTK_VERSION_SUFFIX \
-lvtkRenderingContext2D$$_VTK_VERSION_SUFFIX \
-lvtkChartsCore$$_VTK_VERSION_SUFFIX \
-lvtkRenderingContextOpenGL2$$_VTK_VERSION_SUFFIX \
-lvtkRenderingVolumeOpenGL2$$_VTK_VERSION_SUFFIX
#=============================================================================
```
If you choose to organize and configure your project with CMake instead of Qt’s `qmake` or VS’s `nmake`, please, take a look at this: [https://vtk.org/Wiki/VTK/Tutorials/CMakeListsFile](https://vtk.org/Wiki/VTK/Tutorials/CMakeListsFile).