The intention is to have an option for this in the future. Doing this will make it more likely we will pick up serious issues before the stable build. We would like more people to trial beta and RC builds. We’re trialling this in order to hopefully encourage more people on that track. If you’ve already installed 2023.2, don’t worry, we’ll announce the next beta when it comes out. 2023.2 rc1 won’t detect the stable release as an update so you can leave it to check updates and it will automatically pick up 2023.3 beta 1 when it is out. So 2023.2 rc1 is identical in terms of functionality to 2023.2 (stable). We regularly say that the last RC build is the same as the final stable release and I should stress that is absolutely true (aside from the version number obviously). Those on beta or release candidate builds, if you would like to stay on the “pre-release” build path and automatically get the first 2023.3 beta when it comes out – please stay on 2023.2rc1. We are trying something different with the release of NVDA 2023.2. There are many bug fixes, particularly for braille, Microsoft Office, web browsers and Windows 11. Navigating and reporting formatting in Microsoft Office is improved. There are also new input gestures for OCR and flattened object navigation. There are new braille features, commands, and display support. You can now manually override incompatibility issues with outdated add-ons at your own risk. In the Add-on Store you can browse, search, install and update community add-ons. This release introduces the Add-on Store to replace the Add-ons Manager. Close-up photograph of NVDA logo in notification area.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |