In the COM API, the interface consisted mainly of three methods: StartManipulation(), Manipulate() and EndManipulation(). These methods were called by the ActiveX control class (SpaceX) for all Windows messages posted to the control. The control held a state for the tool, controlling which method to call; depending on the return values from the tool, the state changed and the next method was called.
A concept of "commands" was also used. Each completed user interaction could create an object implementing the ICommand interface; these commands could be used to implement Undo/Redo functionality in an application.

When the C++ API was introduced in version 4.7, a different interface was chosen. This interface consisted of callback methods for various GUI events such as mouse clicks and key presses. The C++ control class did not have to keep track of the state of the tool, it was up to the tool itself.
The C++ interface did not support commands.

In the COM API, the interface consisted mainly of three methods: StartManipulation(), Manipulate() and EndManipulation(). These methods were called by the ActiveX control class (SpaceX) for all Windows messages posted to the control. The control held a state for the tool, controlling which method to call; depending on the return values from the tool, the state changed and the next method was called.
A concept of "commands" was also used. Each completed user interaction could create an object implementing the ICommand interface; these commands could be used to implement Undo/Redo functionality in an application.

When the C++ API was introduced in version 4.7, a different interface was chosen. This interface consisted of callback methods for various GUI events such as mouse clicks and key presses. The C++ control class did not have to keep track of the state of the tool, it was up to the tool itself.
The C++ interface did not support commands.

In the COM API, the interface consisted mainly of three methods: StartManipulation(), Manipulate() and EndManipulation(). These methods were called by the ActiveX control class (SpaceX) for all Windows messages posted to the control. The control held a state for the tool, controlling which method to call; depending on the return values from the tool, the state changed and the next method was called.
A concept of "commands" was also used. Each completed user interaction could create an object implementing the ICommand interface; these commands could be used to implement Undo/Redo functionality in an application.

When the C++ API was introduced in version 4.7, a different interface was chosen. This interface consisted of callback methods for various GUI events such as mouse clicks and key presses. The C++ control class did not have to keep track of the state of the tool, it was up to the tool itself.
The C++ interface did not support commands.

In the COM API, the interface consisted mainly of three methods: StartManipulation(), Manipulate() and EndManipulation(). These methods were called by the ActiveX control class (SpaceX) for all Windows messages posted to the control. The control held a state for the tool, controlling which method to call; depending on the return values from the tool, the state changed and the next method was called.
A concept of "commands" was also used. Each completed user interaction could create an object implementing the ICommand interface; these commands could be used to implement Undo/Redo functionality in an application.

When the C++ API was introduced in version 4.7, a different interface was chosen. This interface consisted of callback methods for various GUI events such as mouse clicks and key presses. The C++ control class did not have to keep track of the state of the tool, it was up to the tool itself.
The C++ interface did not support commands.