If you just want to add some functionality to one of the built-in tools like StandardTool, it is possible to do so, by deriving from the built-in class instead of implementing the full ITool interface. Just override the methods you need, to intercept the mouse and keyboard events you are interested in. Then use the events for your own interaction, or pass them to the base class for its standard interaction handling.

Instead of deriving from a built-in tool, it is also possible to aggregate an instance of a built-in tool in your own ITool implementation, and pass all events you are not interested in to the aggregated tool.

If you just want to add some functionality to one of the built-in tools like StandardTool, it is possible to do so, by deriving from the built-in class instead of implementing the full ITool interface. Just override the methods you need, to intercept the mouse and keyboard events you are interested in. Then use the events for your own interaction, or pass them to the base class for its standard interaction handling.

Instead of deriving from a built-in tool, it is also possible to aggregate an instance of a built-in tool in your own ITool implementation, and pass all events you are not interested in to the aggregated tool.

If you just want to add some functionality to one of the built-in tools like StandardTool, it is possible to do so, by deriving from the built-in class instead of implementing the full ITool interface. Just override the methods you need, to intercept the mouse and keyboard events you are interested in. Then use the events for your own interaction, or pass them to the base class for its standard interaction handling.

Instead of deriving from a built-in tool, it is also possible to aggregate an instance of a built-in tool in your own ITool implementation, and pass all events you are not interested in to the aggregated tool.