Comment 2 by mdcurran on 2010-01-21 22:31
Very happy to add one. However out of interest, how exactly would your app use this.
The way we have designed NVDAControllerClient is so that you can safely call the methods no matter if its running or not. The return code will be non-0 if there was an error communicating with NVDA.
So I guess I just want to be sure (for best performance on your side) that you're not just going to call one NVDA method if it is running. If so, you would have called two methods rather than one.
Also if we did add an isRunning method, it would return 0 if it was running, and an error code (non-zero) if it was not. Is this ok?
Thats just part of how we've chosen to use RPC etc.

Comment 3 by bramd (in reply to comment 2) on 2010-01-21 22:43
Replying to mdcurran:

Very happy to add one. However out of interest, how exactly would your app use this.

Q, I and others work on the Qwitter client for Twitter. We support various speech outputs and have to determine which one to use. If a speech output module is unavailable, aka screenreader is not running, we'll skip it and select the next one.

Of course, how you implement this is your choice. Just do what is consistent with the rest of your interface.

Comment 4 by mdcurran on 2010-01-22 07:36
Implemented in r3480.
nvdaController_testIfRunning()
Like all of the other functions, returns 0 on success (in this case, NVDA is running), non-zero otherwize.
Changes:
State: closed