Hi, I have to say, I really don't like the UX for the upgrade process now. Once you select to do the update, all you hear is the NVDA close sound, then half a minute of silence, then two NVDA start sounds. You don't even confirm update successful or anything, so how can we know if it goes wrong?

EDIT: There's an unmerged pull request to fix this (see replies).
Hey I hate to be a pest, but I'm wondering if anyone has noticed issue #17965. Basically, some code was added to NVDA remote to prevent a controller from sending keys when no machine is connected. The problem is, the check is in the wrong place. If I'm controlling another machine and that machine disconnects, I'm now stuck in limbo, sending keys to nowhere, and I can't toggle back to my own machine because the same check is blocking the toggle and telling me no computer is connected. I'm effectively locked out of my own computer until I use another machine to connect to the same server with the same key, at which point I can go back to the original computer and stop sending keys. Seems like a matter of just rearranging an if statement a bit, but as of a couple of days ago this still affects alpha versions.

Okay, so a question hear. Do you think the XP era voices will be able to handle rateboost? I have a coppy of the latest testing release, and when i turn on rateboost, the pitch sounds off, and the voice sounds like it's breaking. I will be reporting my findings.