Hi Tim,
Thank you for the clarification. In general, we recommend to develop applications using the EyeX Engine API and not by extending functionality in EyeX for Windows. There are two reasons for this:
1) EyeX for Windows might be disabled or unavailable on some systems.
2) EyeX for Windows is under development and future versions might not be backwards-compatible.
I would recommend to build the “voice teleport” function yourself. You only need to subscribe to the gaze data stream (take a look at the samples in the SDK packages) and, when you get the voice command, use the Win32 function SetCursorPos to teleport the cursor to the latest (x,y) coordinates from the data stream.