Open ondrosik opened 4 years ago
Say all now relies on callbacks being fired based on where the speech is reading. I think it is complex to fix this.
Maybe the remote add on needs to be responsible for restoring previous behaviour? Brian
bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users
Steps to reproduce:
Tested with NVDA 2019.3.1 with addons disabled log looks like this (reading this text) Input: kb(laptop):NVDA+s IO - speech.speak (13:29:34.878) - MainThread (2016): Speaking ['Speech mode off'] IO - inputCore.InputManager.executeGesture (13:29:35.754) - winInputHook (2144): Input: kb(laptop):NVDA+a IO - inputCore.InputManager.executeGesture (13:29:39.316) - winInputHook (2144):
I tested this with NVDA 2019.2 with following result:
Input: kb(laptop):NVDA+s IO - speech.speak (13:34:35.846): Speaking [u'Speech mode off'] IO - inputCore.InputManager.executeGesture (13:34:36.447): Input: kb(laptop):NVDA+a DEBUG - queueHandler.registerGeneratorObject (13:34:36.467): Adding generator 11
Windows 10 1809 build 17763.1039