So yes, a quick turnaround this time, but there will be a gap between 2023.1. And 2) The main reason is we are leaving a long gap to 2024.1 in order to ensure the next Python update and other breaking changes going into that build are rock solid before it is released, and also to ensure add-on authors have plenty of time to update their add-ons. We don't expect to need a few weeks for a new stable build to be tested, as that testing has already been done. Hi everyone, Answering the first half a dozen questions in one reply: Shaun asks "Why are we moving towards another release when we only just released a stable build last week?" Two answers to that: 1) Yes we just put out 2023.2 last week, but that had been in beta / RC testing for six weeks, with many features in alpha long before that. Moving the caret as it goes was hot even showing up anymore? Relative, but, for example, in input gestures dialogue, systemĬaret-Reads from the system caret up to the end of the text, So, while the WASAPI output seemed very nicely responsive,Īnd, yes, tried disabling some add-ons that thought could be Read-to-end, or read-to-end with review cursor includedĪlso, even in some of it's own settings dialogues, elementsĪre not being announced as I land on them? One minor, immediate issue - there seems to be no Other more specialist lists such as nvda-devel, nvda-addons and General NVDA mailing list while it has not yet been announced on Strange that this beta release has already been announced on this Have not a version number following the add-on store scheme (X.Y Did you try to restart your computer after installation?Īnd did you try to restart with add-ons disabled?Īs an aside, I have already reported an issue with the add-on that
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |