but there is no reason bar instability in your new product to downgrade to an older nvda. And its not like there are not loads of changes between each versions and those that want to test can.
With a comercial reader I'd understand. At 10:13 p.m. 3/12/2014, you wrote:
Hi, could it be arranged that the add on requires the later versions of nvda, but flags this with advice to upgrade if loaded on older versions of nvda. it would surely be a good thing to get people to use the latest version of access software surely.Brian <mailto:bglists@xxxxxxxxxxxxxxxx>bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:-<mailto:briang1@xxxxxxxxxxxxxxxx>briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff'in the display name field. ----- Original Message ----- From: <mailto:joseph.lee22590@xxxxxxxxx>Joseph Lee To: <mailto:nvda-addons@xxxxxxxxxxxxx>nvda-addons@xxxxxxxxxxxxx Sent: Tuesday, December 02, 2014 2:02 AM Subject: [nvda-addons] Resource Monitor: I guess 4.0 is in order... Hi all,Given new developments with Windows 10 and to let NVDA core use NVDA+Shift+number keys for future commands, I decided to work on RM4.0. Some of the ideas for 4.0 include:· Officially supporting Windows 10: If you are (or will be) using any form of Windows 10, RM 4.0 will be able to detect it and tell you which version of Windows 10 build you are using.· Logical versus physical CPU cores: one of the enhancements in newer PSUtil version is to determine how many logical CPUs are there on your computer. Currently, the add-on counts logical CPUs (for example, if you have a dual core CPU with Hyper-Threading on, your computer will say it has four CPUs). One option is to just count physical cores, but given that some of us use computers with HT-capable processors, Im considering leaving this as is (this is used when reporting CPU activity).· Gesture reassignments: To allow NVDA core to use NVDA+Shift+number keys for future commands, Im thinking of using two approaches to prepare for that scenario. Plan A is to unassign NVDA+Shift+number keys so users can assign their favorite gestures to needed resource monitor announcements, and plan B calls for making RM commands a layer that is, press NvDA+Shift+E, then press a number key to hear RM announcements. Both have advantages and drawbacks: plan A allows users to assign gestures to resource announcements that are needed the most, and because of this, add-on 4.0 will require NVDA 2013.3 or later in order to function correctly and documentation change is needed; plan B allows a single layer to house all the needed RM commands, which also requires changing documentation and can be used in versions as old as NVDA 2013.2.Of the above ideas, Id like to ask for your opinions on the last item unassigned gestures versus layer approach. If one of the ideas is adopted, this would allow NVDA core to use the commands formerly taken by RM add-on for other gestures, such as enhanced navigator object macros (to keep an eye on up to five objects at once) and other commands.Thanks. Cheers, Joseph
---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx. To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx. If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx. Community addons can be found here: http://addons.nvda-project.org
