Just so we’re on the same page, what you described is exactly what I built. It didn’t take long, and I did base it on the C code example you mentioned. Nevertheless, I still think that for the average voice-recognition user it’s asking a lot for them to reimplement the EyeX Interaction hooks themselves. If the software could respond to simulated keypresses like every other application I use, it would not have required any custom code. I’m a developer, and this is an SDK, so I’m happy to do this myself, but this is really something that should be addressed for the end product.