Menu
▾
▴
nvda-devel — NVDA screen reader development
This list is closed, nobody may subscribe to it.
| 2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
(392) |
May
(234) |
Jun
(332) |
Jul
(409) |
Aug
(236) |
Sep
(208) |
Oct
(283) |
Nov
(311) |
Dec
(272) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(179) |
Feb
(255) |
Mar
(218) |
Apr
(202) |
May
(302) |
Jun
(211) |
Jul
(396) |
Aug
(366) |
Sep
(237) |
Oct
(204) |
Nov
(281) |
Dec
(264) |
| 2010 |
Jan
(480) |
Feb
(663) |
Mar
(673) |
Apr
(508) |
May
(903) |
Jun
(618) |
Jul
(802) |
Aug
(990) |
Sep
(869) |
Oct
(733) |
Nov
(825) |
Dec
(676) |
| 2011 |
Jan
(667) |
Feb
(630) |
Mar
(491) |
Apr
(694) |
May
(902) |
Jun
(1029) |
Jul
(637) |
Aug
(679) |
Sep
(725) |
Oct
(735) |
Nov
(937) |
Dec
(445) |
| 2012 |
Jan
(486) |
Feb
(586) |
Mar
(679) |
Apr
(861) |
May
(1064) |
Jun
(887) |
Jul
(839) |
Aug
(807) |
Sep
(775) |
Oct
(320) |
Nov
(293) |
Dec
(230) |
| 2013 |
Jan
(197) |
Feb
(337) |
Mar
(471) |
Apr
(434) |
May
(191) |
Jun
(201) |
Jul
(332) |
Aug
(360) |
Sep
(333) |
Oct
(153) |
Nov
(265) |
Dec
(227) |
| 2014 |
Jan
(226) |
Feb
(410) |
Mar
(324) |
Apr
(212) |
May
(182) |
Jun
(200) |
Jul
(292) |
Aug
(292) |
Sep
(215) |
Oct
(204) |
Nov
(155) |
Dec
(190) |
| 2015 |
Jan
(216) |
Feb
(158) |
Mar
(101) |
Apr
(118) |
May
(163) |
Jun
(205) |
Jul
(255) |
Aug
(202) |
Sep
(143) |
Oct
(148) |
Nov
(298) |
Dec
(168) |
| 2016 |
Jan
(124) |
Feb
(149) |
Mar
(183) |
Apr
(245) |
May
(176) |
Jun
(149) |
Jul
(162) |
Aug
(161) |
Sep
(109) |
Oct
(172) |
Nov
(135) |
Dec
(173) |
| 2017 |
Jan
(136) |
Feb
(97) |
Mar
(93) |
Apr
(145) |
May
(155) |
Jun
(130) |
Jul
(152) |
Aug
(76) |
Sep
(80) |
Oct
(220) |
Nov
(68) |
Dec
(79) |
| 2018 |
Jan
(44) |
Feb
(60) |
Mar
(14) |
Apr
(34) |
May
(35) |
Jun
(92) |
Jul
(89) |
Aug
(89) |
Sep
(64) |
Oct
(54) |
Nov
(40) |
Dec
(111) |
| 2019 |
Jan
(54) |
Feb
(48) |
Mar
(37) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael C. <mi...@ku...> - 2019-03-20 05:43:27
|
Hi all, Recently Sourceforge has started producing 404 errors on certain list pages, plus some people have been reporting that they cannot post to this list once they have subscribed. Based on this and other reasons, NV Access has decided that it is best to move this list to groups.io. Sourceforge is no longer a suitable platform for such a project as ours. I have created a new development list on groups.io: https://nvda-devel.groups.io Please use the groups.io list for future discussion about NVDA development. After this post, I shall be making this Sourceforge list read-only, and investigating how I can transfer previous posts over to groups.io. I have not yet filled in all public information, but I figure people can start subscribing before this is complete. See you all on groups.io. Mick |
|
From: Mgr. J. C. <jan...@vo...> - 2019-03-19 20:12:46
|
Dear core developers of NVDA, Does somebody of us know, how complex would be to redesign some parts of NVDA so SHIFT+arrow keys would correctly announce assigned words, characters or lines also on Delphi based components? Or somebody would had to convince Delphi developers to develop their GUI toolkit so NVDA would announce assigned data when SHIFT+ arrow key will be used when focus is actually on Editable field? Here is some info from NVDA navigator object. name: None role: ROLE_EDITABLETEXT states: STATE_FOCUSABLE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <baseObject.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x05786F70> Python class mro: (<class 'baseObject.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.DisplayModelEditableText'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: RectLTWH(left=249, top=216, width=1072, height=297) value: None appModule: <'appModuleHandler' (appName u'lazarus', process ID 197456) at address 5994730> appModule.productName: u'Lazarus IDE' appModule.productVersion: u'' TextInfo: <class 'displayModel.EditableTextDisplayModelTextInfo'> windowHandle: 1639282 windowClassName: u'Window' windowControlID: 239291936 windowStyle: 1446051840 windowThreadID: 196100 windowText: u'' displayText: u"35 LEditName2 := TEdit.Create(Self); . . LButtonSave := TButton.Create(Self); . LButtonSave.Caption := 'Vyhodnotit odpov\u011bdi'; . LButtonSave.OnClick := @ButtonClick;40 (* . *) . (* . *) . end;45 . procedure TFormMain.ButtonClick(A: T" (truncated) IAccessibleObject: <POINTER(IAccessible) ptr=0x7cb32c8 at 5b7c6c0> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=1639282, objectID=-4, childID=0 IAccessible accName: None IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None |
|
From: <jos...@gm...> - 2019-03-19 15:58:57
|
Hi everyone, For people reading the NVDA add-on development guide: you'll see huge changes coming to that guide in the next few days. The biggest change is introduction of scratchpad directory and changes to examples as a result. Specifically: * Any examples that refer to the old folder structure will be rewritten to say that you can use these examples with scratchpad turned on. * I'll highlight Advanced panel and the reason for existence of scratchpad setting. * Add-on compatibility range (minimum/last tested) will be mentioned and demonstrated. Along with this, the new API docs for 2019.1 will be uploaded to my website within 48 hours after release of 2019.1 stable. Cheers, Joseph |
|
From: Karl-Otto R. <kar...@ma...> - 2019-03-18 21:19:39
|
Hi! As a Visual Studio 2017 developer I use it daily and the background compilation sometimes drags down performance of NVDA, the speech lags a lot. This is what one have to live with if one wants the InteliSense and other nice-to-have features. When VS stops on a breakpoint it takes at least 10 to 20 seconds before NVDA is ready to read as expected. What can I do to try to log this to see what might be the problem? Sometimes NVDA won't come to life so I have to start over. Often I quit NVDA just before I know that I'll hit the breakpoint, i e before clicking on a button or so on, and when the code editor is shown with the breakpoint I start NVDA again. Best regards Karl-Otto Karl-Otto Rosenqvist Mawingu Orgnr: 750804-3937 +46 (0)701 75 98 56 kar...@ma... Den 2019-03-17 kl. 23:37, skrev francisco del roio: > Hello people, > > I've downloaded Visual Studio 2019 RC to test nvda against it. > > I see a lower performance due to constant changes in the various views. > Sometimes it is simply unusable. > > Can I do some tests to help improving this? > > Cheers, > |
|
From: francisco d. r. <fra...@ho...> - 2019-03-17 22:37:50
|
Hello people, I've downloaded Visual Studio 2019 RC to test nvda against it. I see a lower performance due to constant changes in the various views. Sometimes it is simply unusable. Can I do some tests to help improving this? Cheers, -- Cuando tus fuerzas terminan, las de mi Dios comienzan. |
|
From: francisco d. r. <fra...@ho...> - 2019-03-15 11:13:48
|
Hello, I'm experimenting a strange behavior with various UIA documents, cannot confirm if it occurs with WPF document view too, but I will try to explain myself. For example, you have a word document with a paragraph followed by a list, without a blank line between them. If you read the last line of the paragraph, the numeration is presented in the end of the line. Next you begin reading the list as normal, except that at the end of the item, you get announced the next item numeration again. It occurs with some elements in edge, such links, tables and lists. You're reading the last item of the list and it says, at the end of the list that the list ends, but in Firefox/Chrome it doesn't occurs. Cheers, -- Cuando tus fuerzas terminan, las de mi Dios comienzan. |
|
From: John J. B. <joh...@ab...> - 2019-03-14 07:36:39
|
Hello, It would be nice to make the BrailleExtender feature of chosing two or more outpuut tables part of the standard Braille options. I have a lot of files that have already been translated into Braille. Chosing between output tables is really the only BrailleExtender feature that I need. Thanks, John -- John J. Boyer Email: joh...@ab... website: http://www.abilitiessoft.org Status: Company dissolved but website and email addresses live. Location: Madison, Wisconsin, USA Mission: developing assistive technology software and providing STEM services that are available at no cost |
|
From: Heiko F. <Hei...@ms...> - 2019-03-12 10:37:53
|
Hi Ralf, well we are running office 365 so it seems to be the trouble there too. Mit freundlichen Grüßen Dipl.-Inf (FH) Heiko Folkerts Softwareentwicklung und -Design -- _______________________________________________________ msg DAVID GmbH · Mittelweg 7 · 38106 Braunschweig Tel.: +49 531 24379-14 Fax.: +49 531 24379-79 E-Mail: mailto:hei...@ms... WWW: https://www.msg-david.de Eintragung: Amtsgericht Braunschweig, HRB 3167 Geschäftsführer: Andreas Lehmann, Dirk Schäfer, Dr. Andreas Scholz _______________________________________________________ -----Ursprüngliche Nachricht----- Von: Ralf Kefferpuetz <ral...@el...> Gesendet: Dienstag, 12. März 2019 08:45 An: 'NVDA screen reader development' <nvd...@li...> Betreff: Re: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi Heiko, I noticed the same or similar when presenting with Powerpoint or Excel. I'm not able to read with NVDA what I'm presenting. I had this experience with Office 2013 in combination with skype for business 2015. Now I'm on Office 365 plus at work, but I never tested it with that new version of office and skype for business. If you like we can test it at the weekend in a conference, trying with some browsers and some Office programs. With the results we got then we can create new NVDA issues. Regards, Ralf -----Original Message----- From: Heiko Folkerts <he...@hf...> Sent: Montag, 11. März 2019 20:55 To: nvd...@li... Subject: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi all, I noticed that when I am in a skype conversation and I present my desktop then I cannot change between focus and read mode in firefox and cannot navigate a page. Is this known/wanted or should I file a ticket fort hat? A quick search didn't reveal any issues. Heiko Machen Sie mit und teilen Sie Ihr Wissen auf www.besonderetipps.de Bitte schützen Sie meine und Ihre Privatsphäre und verwenden Sie PGP. pub 2048R/B5F8D556 2014-08-06 Schl.-Fingerabdruck = 758D DA37 1DA1 1E2F 7CDD 60A2 F3F4 1E8D B5F8 D556 uid [ uneing.] Heiko Folkerts <hei...@bf...> uid [ uneing.] Heiko Folkerts <he...@hf...> uid [ uneing.] Heiko Folkerts <hei...@we...> sub 4096g/BC0D1006 2015-08-27 [verfllt: 2016-08-26] _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Ralf K. <ral...@el...> - 2019-03-12 09:31:57
|
It did exist in all stable releases for 2018... again, need to do more testing -----Original Message----- From: Brians old account via Nvda-devel <nvd...@li...> Sent: Dienstag, 12. März 2019 09:27 To: NVDA screen reader development <nvd...@li...> Cc: Brians old account <bg...@bl...> Subject: Re: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation I do not use Skype myself but wondered if the focus issue might be related to the previous thread. Did this exist in the previous stable release? Brian bg...@li... Brian Gaff's other account. ----- Original Message ----- From: "Ralf Kefferpuetz" <ral...@el...> To: "'NVDA screen reader development'" <nvd...@li...> Sent: Tuesday, March 12, 2019 7:45 AM Subject: Re: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi Heiko, I noticed the same or similar when presenting with Powerpoint or Excel. I'm not able to read with NVDA what I'm presenting. I had this experience with Office 2013 in combination with skype for business 2015. Now I'm on Office 365 plus at work, but I never tested it with that new version of office and skype for business. If you like we can test it at the weekend in a conference, trying with some browsers and some Office programs. With the results we got then we can create new NVDA issues. Regards, Ralf -----Original Message----- From: Heiko Folkerts <he...@hf...> Sent: Montag, 11. März 2019 20:55 To: nvd...@li... Subject: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi all, I noticed that when I am in a skype conversation and I present my desktop then I cannot change between focus and read mode in firefox and cannot navigate a page. Is this known/wanted or should I file a ticket fort hat? A quick search didn't reveal any issues. Heiko Machen Sie mit und teilen Sie Ihr Wissen auf www.besonderetipps.de Bitte schützen Sie meine und Ihre Privatsphäre und verwenden Sie PGP. pub 2048R/B5F8D556 2014-08-06 Schl.-Fingerabdruck = 758D DA37 1DA1 1E2F 7CDD 60A2 F3F4 1E8D B5F8 D556 uid [ uneing.] Heiko Folkerts <hei...@bf...> uid [ uneing.] Heiko Folkerts <he...@hf...> uid [ uneing.] Heiko Folkerts <hei...@we...> sub 4096g/BC0D1006 2015-08-27 [verf"llt: 2016-08-26] _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Brians o. a. <bg...@bl...> - 2019-03-12 08:27:36
|
I do not use Skype myself but wondered if the focus issue might be related to the previous thread. Did this exist in the previous stable release? Brian bg...@li... Brian Gaff's other account. ----- Original Message ----- From: "Ralf Kefferpuetz" <ral...@el...> To: "'NVDA screen reader development'" <nvd...@li...> Sent: Tuesday, March 12, 2019 7:45 AM Subject: Re: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi Heiko, I noticed the same or similar when presenting with Powerpoint or Excel. I'm not able to read with NVDA what I'm presenting. I had this experience with Office 2013 in combination with skype for business 2015. Now I'm on Office 365 plus at work, but I never tested it with that new version of office and skype for business. If you like we can test it at the weekend in a conference, trying with some browsers and some Office programs. With the results we got then we can create new NVDA issues. Regards, Ralf -----Original Message----- From: Heiko Folkerts <he...@hf...> Sent: Montag, 11. März 2019 20:55 To: nvd...@li... Subject: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi all, I noticed that when I am in a skype conversation and I present my desktop then I cannot change between focus and read mode in firefox and cannot navigate a page. Is this known/wanted or should I file a ticket fort hat? A quick search didn't reveal any issues. Heiko Machen Sie mit und teilen Sie Ihr Wissen auf www.besonderetipps.de Bitte schützen Sie meine und Ihre Privatsphäre und verwenden Sie PGP. pub 2048R/B5F8D556 2014-08-06 Schl.-Fingerabdruck = 758D DA37 1DA1 1E2F 7CDD 60A2 F3F4 1E8D B5F8 D556 uid [ uneing.] Heiko Folkerts <hei...@bf...> uid [ uneing.] Heiko Folkerts <he...@hf...> uid [ uneing.] Heiko Folkerts <hei...@we...> sub 4096g/BC0D1006 2015-08-27 [verf"llt: 2016-08-26] _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Brians o. a. <bg...@bl...> - 2019-03-12 08:25:37
|
Here are the add ons I have in the installed copy of 2019.1 beta
add ons updater
Applications dictionary
audio themes
Dropbox, but no longer is working
Winamp extender
Dumb clipboard announcements
Focus highlight now disabled
Golden Cursor. (This needs a new name in my view)
Goldwave
Indent nav
Mozilla enhancements
Open link with
Svox Pico. Only used for demo purposes
Resource monitor
Speech player in espeak. Useful to check current espeak pronounciations etc.
Systray list
Text nav
Toolbar explorer
And that is it.
Brian
Brian
bg...@li...
Brian Gaff's other account.
----- Original Message -----
From: "Ethin Probst" <har...@gm...>
To: "NVDA screen reader development" <nvd...@li...>
Sent: Monday, March 11, 2019 6:49 PM
Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
> This happens to me too where I'll be doing something and NVDA will
> lock the focus on/in a particular applications window and I can't do
> anything -- or at least NVDA acts like I can't. The lock-up remains
> even after I've closed the offending application (which is weird).
> Restarting NVDA is the only solution I've found.
>
> On 3/11/19, Brian's Mail list account BY via Nvda-devel
> <nvd...@li...> wrote:
>> PS everyone will be at the exhibition on the states this week so I doubt
>> many will see it till next week so plenty of time to find a more useful
>> demo
>> with nvda/f1 and no add onse. Sadly due to it working again after a
>> reboot
>> its going to be difficult to get at least two issues to happen one when
>> for
>> day to day, and one when add ons arare removed.
>> Brian
>>
>> bg...@bl...
>> Sent via blueyonder.
>> Please address personal E-mail to:-
>> br...@bl..., putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Michel Such" <mic...@fr...>
>> To: "Brian's Mail list account BY via Nvda-devel"
>> <nvd...@li...>
>> Sent: Monday, March 11, 2019 10:01 AM
>> Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
>>
>>
>>> Hi,
>>>
>>>
>>> I sometimes notice the same problem, especially in explorer.
>>>
>>>
>>> Michel Such
>>>
>>> Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a
>>> écrit
>>>
>>> :
>>>> A kind of lock up happens now and again where only rebooting nvda seems
>>>> to cure it, but it seems to happen randomly. Sods law being what it is,
>>>> this mornings happening was in a version of the Outlook Express
>>>> spellchecker, but yesterday it was in Explorer. As yet I have not been
>>>> able to test with no add ons or do an nvda/f1, but it looks like the
>>>> focus stays on an item, wherever it may be and cannot audibly be moved,
>>>> though it may well move in reality, I could not say at this time. I did
>>>> do the log for this, and no actual sounding error occurs it just seems
>>>> to
>>>>
>>>> ignore you and repeat.
>>>> Unfortunately because this one happened in Outlook express nobody will
>>>> be
>>>>
>>>> able to duplicate it, so I'll continue monitoring to see if I can catch
>>>> it in a more generic place and do the required tests and then do an
>>>> issue
>>>>
>>>> in github if it turns out to be nvda and not an add on.
>>>>
>>>> Here is the log I have anyway.
>>>>
>>>> IO - inputCore.InputManager.executeGesture (08:56:49.832):
>>>> Input: kb(desktop):enter
>>>> IO - speech.speak (08:56:49.948):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
>>>> Dictionary:\ninagine']
>>>> IO - speech.speak (08:56:49.950):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
>>>> IO - speech.speak (08:56:49.950):
>>>> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.665):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483633: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.667):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.667):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483631: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483592: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483616: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483593: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.671):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.466):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.473):
>>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.674):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.691):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.874):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.880):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:56.338):
>>>> Input: kb(desktop):shift+tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:56.346):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:57.665):
>>>> Input: kb(desktop):downArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:57.788):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:56:58.065):
>>>> Input: kb(desktop):upArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:58.194):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:56:59.562):
>>>> Input: kb(desktop):downArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:59.694):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:00.515):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.526):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:00.762):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.778):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483644: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.780):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.782):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:02.072):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:02.086):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:02.704):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:02.720):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:02.829):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:03.585):
>>>> Input: kb(desktop):upArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:03.611):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:03.717):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:09.408):
>>>> Input: kb(desktop):escape
>>>> IO - inputCore.InputManager.executeGesture (08:57:10.461):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:10.490):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:10.596):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:11.844):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:11.862):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483640: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:11.969):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:12.329):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:12.348):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:12.457):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:18.473):
>>>> Input: kb(desktop):control+alt+r
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:18.483):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>>> IO - speech.speak (08:57:18.539):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
>>>> IO - speech.speak (08:57:18.680):
>>>> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log
>>>> terminal']
>>>>
>>>>
>>>> Anyway, I'll keep an ear on it.
>>>> Brian
>>>> bg...@bl...
>>>> Sent via blueyonder.
>>>> Please address personal E-mail to:-
>>>> br...@bl..., putting 'Brian Gaff'
>>>> in the display name field.
>>>>
>>>>
>>>> _______________________________________________
>>>> Nvda-devel mailing list
>>>> Nvd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> Nvd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvd...@li...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
> --
> Signed,
> Ethin D. Probst
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
|
|
From: Brians o. a. <bg...@bl...> - 2019-03-12 08:14:21
|
Yes how localised the lock up is seems to vary between bits of software. I'm
sure its some minor regression but figuring out the actual requirements for
it to occur is seemingly not easy.
Being as it takes a long time to happen turning off all add ons for so long
is impractical.
As a matter of interest what add ons do you have installed. I'm thinking if
you have focus highlight it might be worth turning it off?
Brian
bg...@li...
Brian Gaff's other account.
----- Original Message -----
From: "Ethin Probst" <har...@gm...>
To: "NVDA screen reader development" <nvd...@li...>
Sent: Monday, March 11, 2019 6:49 PM
Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
> This happens to me too where I'll be doing something and NVDA will
> lock the focus on/in a particular applications window and I can't do
> anything -- or at least NVDA acts like I can't. The lock-up remains
> even after I've closed the offending application (which is weird).
> Restarting NVDA is the only solution I've found.
>
> On 3/11/19, Brian's Mail list account BY via Nvda-devel
> <nvd...@li...> wrote:
>> PS everyone will be at the exhibition on the states this week so I doubt
>> many will see it till next week so plenty of time to find a more useful
>> demo
>> with nvda/f1 and no add onse. Sadly due to it working again after a
>> reboot
>> its going to be difficult to get at least two issues to happen one when
>> for
>> day to day, and one when add ons arare removed.
>> Brian
>>
>> bg...@bl...
>> Sent via blueyonder.
>> Please address personal E-mail to:-
>> br...@bl..., putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message -----
>> From: "Michel Such" <mic...@fr...>
>> To: "Brian's Mail list account BY via Nvda-devel"
>> <nvd...@li...>
>> Sent: Monday, March 11, 2019 10:01 AM
>> Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
>>
>>
>>> Hi,
>>>
>>>
>>> I sometimes notice the same problem, especially in explorer.
>>>
>>>
>>> Michel Such
>>>
>>> Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a
>>> écrit
>>>
>>> :
>>>> A kind of lock up happens now and again where only rebooting nvda seems
>>>> to cure it, but it seems to happen randomly. Sods law being what it is,
>>>> this mornings happening was in a version of the Outlook Express
>>>> spellchecker, but yesterday it was in Explorer. As yet I have not been
>>>> able to test with no add ons or do an nvda/f1, but it looks like the
>>>> focus stays on an item, wherever it may be and cannot audibly be moved,
>>>> though it may well move in reality, I could not say at this time. I did
>>>> do the log for this, and no actual sounding error occurs it just seems
>>>> to
>>>>
>>>> ignore you and repeat.
>>>> Unfortunately because this one happened in Outlook express nobody will
>>>> be
>>>>
>>>> able to duplicate it, so I'll continue monitoring to see if I can catch
>>>> it in a more generic place and do the required tests and then do an
>>>> issue
>>>>
>>>> in github if it turns out to be nvda and not an add on.
>>>>
>>>> Here is the log I have anyway.
>>>>
>>>> IO - inputCore.InputManager.executeGesture (08:56:49.832):
>>>> Input: kb(desktop):enter
>>>> IO - speech.speak (08:56:49.948):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
>>>> Dictionary:\ninagine']
>>>> IO - speech.speak (08:56:49.950):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
>>>> IO - speech.speak (08:56:49.950):
>>>> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.665):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483633: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.667):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.667):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483631: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483592: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.668):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483616: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483593: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.670):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.671):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:51.680):
>>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.466):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.473):
>>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.674):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.691):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:54.874):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:54.880):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:56.338):
>>>> Input: kb(desktop):shift+tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:56:56.346):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:56:57.665):
>>>> Input: kb(desktop):downArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:57.788):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:56:58.065):
>>>> Input: kb(desktop):upArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:58.194):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:56:59.562):
>>>> Input: kb(desktop):downArrow
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:56:59.694):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:00.515):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.526):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:00.762):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.778):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483644: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.779):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID 0: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.780):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:00.782):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:02.072):
>>>> Input: kb(desktop):tab
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:02.086):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>>> IO - inputCore.InputManager.executeGesture (08:57:02.704):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:02.720):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:02.829):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:03.585):
>>>> Input: kb(desktop):upArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:03.611):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:03.717):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:09.408):
>>>> Input: kb(desktop):escape
>>>> IO - inputCore.InputManager.executeGesture (08:57:10.461):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:10.490):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:10.596):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:11.844):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:11.862):
>>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>>> childID -2147483640: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:11.969):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:12.329):
>>>> Input: kb(desktop):downArrow
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:12.348):
>>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
>>>> Caret didn't move before timeout. Elapsed: 100 ms
>>>> IO - speech.speak (08:57:12.457):
>>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>>> IO - inputCore.InputManager.executeGesture (08:57:18.473):
>>>> Input: kb(desktop):control+alt+r
>>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>>> (08:57:18.483):
>>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>>> IO - speech.speak (08:57:18.539):
>>>> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
>>>> IO - speech.speak (08:57:18.680):
>>>> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log
>>>> terminal']
>>>>
>>>>
>>>> Anyway, I'll keep an ear on it.
>>>> Brian
>>>> bg...@bl...
>>>> Sent via blueyonder.
>>>> Please address personal E-mail to:-
>>>> br...@bl..., putting 'Brian Gaff'
>>>> in the display name field.
>>>>
>>>>
>>>> _______________________________________________
>>>> Nvda-devel mailing list
>>>> Nvd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> Nvd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>>
>>
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvd...@li...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
> --
> Signed,
> Ethin D. Probst
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
|
|
From: Ralf K. <ral...@el...> - 2019-03-12 07:57:49
|
Hi Heiko, I noticed the same or similar when presenting with Powerpoint or Excel. I'm not able to read with NVDA what I'm presenting. I had this experience with Office 2013 in combination with skype for business 2015. Now I'm on Office 365 plus at work, but I never tested it with that new version of office and skype for business. If you like we can test it at the weekend in a conference, trying with some browsers and some Office programs. With the results we got then we can create new NVDA issues. Regards, Ralf -----Original Message----- From: Heiko Folkerts <he...@hf...> Sent: Montag, 11. März 2019 20:55 To: nvd...@li... Subject: [Nvda-devel] NVDA cannot navigate in mozilla firefox during a skype presentation Hi all, I noticed that when I am in a skype conversation and I present my desktop then I cannot change between focus and read mode in firefox and cannot navigate a page. Is this known/wanted or should I file a ticket fort hat? A quick search didn't reveal any issues. Heiko Machen Sie mit und teilen Sie Ihr Wissen auf www.besonderetipps.de Bitte schützen Sie meine und Ihre Privatsphäre und verwenden Sie PGP. pub 2048R/B5F8D556 2014-08-06 Schl.-Fingerabdruck = 758D DA37 1DA1 1E2F 7CDD 60A2 F3F4 1E8D B5F8 D556 uid [ uneing.] Heiko Folkerts <hei...@bf...> uid [ uneing.] Heiko Folkerts <he...@hf...> uid [ uneing.] Heiko Folkerts <hei...@we...> sub 4096g/BC0D1006 2015-08-27 [verfllt: 2016-08-26] _______________________________________________ Nvda-devel mailing list Nvd...@li... https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Heiko F. <he...@hf...> - 2019-03-11 20:06:51
|
Hi all, I noticed that when I am in a skype conversation and I present my desktop then I cannot change between focus and read mode in firefox and cannot navigate a page. Is this known/wanted or should I file a ticket fort hat? A quick search didn't reveal any issues. Heiko Machen Sie mit und teilen Sie Ihr Wissen auf www.besonderetipps.de Bitte schützen Sie meine und Ihre Privatsphäre und verwenden Sie PGP. pub 2048R/B5F8D556 2014-08-06 Schl.-Fingerabdruck = 758D DA37 1DA1 1E2F 7CDD 60A2 F3F4 1E8D B5F8 D556 uid [ uneing.] Heiko Folkerts <hei...@bf...> uid [ uneing.] Heiko Folkerts <he...@hf...> uid [ uneing.] Heiko Folkerts <hei...@we...> sub 4096g/BC0D1006 2015-08-27 [verfllt: 2016-08-26] |
|
From: Ethin P. <har...@gm...> - 2019-03-11 18:49:49
|
This happens to me too where I'll be doing something and NVDA will
lock the focus on/in a particular applications window and I can't do
anything -- or at least NVDA acts like I can't. The lock-up remains
even after I've closed the offending application (which is weird).
Restarting NVDA is the only solution I've found.
On 3/11/19, Brian's Mail list account BY via Nvda-devel
<nvd...@li...> wrote:
> PS everyone will be at the exhibition on the states this week so I doubt
> many will see it till next week so plenty of time to find a more useful demo
> with nvda/f1 and no add onse. Sadly due to it working again after a reboot
> its going to be difficult to get at least two issues to happen one when for
> day to day, and one when add ons arare removed.
> Brian
>
> bg...@bl...
> Sent via blueyonder.
> Please address personal E-mail to:-
> br...@bl..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message -----
> From: "Michel Such" <mic...@fr...>
> To: "Brian's Mail list account BY via Nvda-devel"
> <nvd...@li...>
> Sent: Monday, March 11, 2019 10:01 AM
> Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
>
>
>> Hi,
>>
>>
>> I sometimes notice the same problem, especially in explorer.
>>
>>
>> Michel Such
>>
>> Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a écrit
>>
>> :
>>> A kind of lock up happens now and again where only rebooting nvda seems
>>> to cure it, but it seems to happen randomly. Sods law being what it is,
>>> this mornings happening was in a version of the Outlook Express
>>> spellchecker, but yesterday it was in Explorer. As yet I have not been
>>> able to test with no add ons or do an nvda/f1, but it looks like the
>>> focus stays on an item, wherever it may be and cannot audibly be moved,
>>> though it may well move in reality, I could not say at this time. I did
>>> do the log for this, and no actual sounding error occurs it just seems to
>>>
>>> ignore you and repeat.
>>> Unfortunately because this one happened in Outlook express nobody will be
>>>
>>> able to duplicate it, so I'll continue monitoring to see if I can catch
>>> it in a more generic place and do the required tests and then do an issue
>>>
>>> in github if it turns out to be nvda and not an add on.
>>>
>>> Here is the log I have anyway.
>>>
>>> IO - inputCore.InputManager.executeGesture (08:56:49.832):
>>> Input: kb(desktop):enter
>>> IO - speech.speak (08:56:49.948):
>>> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
>>> Dictionary:\ninagine']
>>> IO - speech.speak (08:56:49.950):
>>> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
>>> IO - speech.speak (08:56:49.950):
>>> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.665):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483633: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.667):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.667):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483631: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.668):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.668):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483592: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.668):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483616: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.670):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.670):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483593: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.670):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.671):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.680):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.680):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.680):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:51.680):
>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:56:54.466):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:54.473):
>>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:56:54.674):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:54.691):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:56:54.874):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:54.880):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:56:56.338):
>>> Input: kb(desktop):shift+tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:56:56.346):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:56:57.665):
>>> Input: kb(desktop):downArrow
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:56:57.788):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:56:58.065):
>>> Input: kb(desktop):upArrow
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:56:58.194):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:56:59.562):
>>> Input: kb(desktop):downArrow
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:56:59.694):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:00.515):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.526):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:57:00.762):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.778):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483644: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.779):
>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.779):
>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.779):
>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>> childID 0: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.780):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:00.782):
>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:57:02.072):
>>> Input: kb(desktop):tab
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:02.086):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>> IO - inputCore.InputManager.executeGesture (08:57:02.704):
>>> Input: kb(desktop):downArrow
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:02.720):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:57:02.829):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:03.585):
>>> Input: kb(desktop):upArrow
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:03.611):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:57:03.717):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:09.408):
>>> Input: kb(desktop):escape
>>> IO - inputCore.InputManager.executeGesture (08:57:10.461):
>>> Input: kb(desktop):downArrow
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:10.490):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:57:10.596):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:11.844):
>>> Input: kb(desktop):downArrow
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:11.862):
>>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>>> childID -2147483640: [Error -2147024809] The parameter is incorrect
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:57:11.969):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:12.329):
>>> Input: kb(desktop):downArrow
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:12.348):
>>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
>>> Caret didn't move before timeout. Elapsed: 100 ms
>>> IO - speech.speak (08:57:12.457):
>>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>>> IO - inputCore.InputManager.executeGesture (08:57:18.473):
>>> Input: kb(desktop):control+alt+r
>>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>>> (08:57:18.483):
>>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>>> IO - speech.speak (08:57:18.539):
>>> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
>>> IO - speech.speak (08:57:18.680):
>>> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
>>>
>>>
>>> Anyway, I'll keep an ear on it.
>>> Brian
>>> bg...@bl...
>>> Sent via blueyonder.
>>> Please address personal E-mail to:-
>>> br...@bl..., putting 'Brian Gaff'
>>> in the display name field.
>>>
>>>
>>> _______________________________________________
>>> Nvda-devel mailing list
>>> Nvd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvd...@li...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
--
Signed,
Ethin D. Probst
|
|
From: Brian's M. l. a. B. <bg...@bl...> - 2019-03-11 10:41:21
|
PS everyone will be at the exhibition on the states this week so I doubt
many will see it till next week so plenty of time to find a more useful demo
with nvda/f1 and no add onse. Sadly due to it working again after a reboot
its going to be difficult to get at least two issues to happen one when for
day to day, and one when add ons arare removed.
Brian
bg...@bl...
Sent via blueyonder.
Please address personal E-mail to:-
br...@bl..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Michel Such" <mic...@fr...>
To: "Brian's Mail list account BY via Nvda-devel"
<nvd...@li...>
Sent: Monday, March 11, 2019 10:01 AM
Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
> Hi,
>
>
> I sometimes notice the same problem, especially in explorer.
>
>
> Michel Such
>
> Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a écrit
> :
>> A kind of lock up happens now and again where only rebooting nvda seems
>> to cure it, but it seems to happen randomly. Sods law being what it is,
>> this mornings happening was in a version of the Outlook Express
>> spellchecker, but yesterday it was in Explorer. As yet I have not been
>> able to test with no add ons or do an nvda/f1, but it looks like the
>> focus stays on an item, wherever it may be and cannot audibly be moved,
>> though it may well move in reality, I could not say at this time. I did
>> do the log for this, and no actual sounding error occurs it just seems to
>> ignore you and repeat.
>> Unfortunately because this one happened in Outlook express nobody will be
>> able to duplicate it, so I'll continue monitoring to see if I can catch
>> it in a more generic place and do the required tests and then do an issue
>> in github if it turns out to be nvda and not an add on.
>>
>> Here is the log I have anyway.
>>
>> IO - inputCore.InputManager.executeGesture (08:56:49.832):
>> Input: kb(desktop):enter
>> IO - speech.speak (08:56:49.948):
>> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
>> Dictionary:\ninagine']
>> IO - speech.speak (08:56:49.950):
>> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
>> IO - speech.speak (08:56:49.950):
>> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.665):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483633: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.667):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.667):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483631: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483592: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483616: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483593: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.671):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.466):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.473):
>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.674):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.691):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.874):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.880):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:56.338):
>> Input: kb(desktop):shift+tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:56.346):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:57.665):
>> Input: kb(desktop):downArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:57.788):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:56:58.065):
>> Input: kb(desktop):upArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:58.194):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:56:59.562):
>> Input: kb(desktop):downArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:59.694):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:00.515):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.526):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:00.762):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.778):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483644: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.780):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.782):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:02.072):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:02.086):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:02.704):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:02.720):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:02.829):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:03.585):
>> Input: kb(desktop):upArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:03.611):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:03.717):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:09.408):
>> Input: kb(desktop):escape
>> IO - inputCore.InputManager.executeGesture (08:57:10.461):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:10.490):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:10.596):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:11.844):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:11.862):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483640: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:11.969):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:12.329):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:12.348):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:12.457):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:18.473):
>> Input: kb(desktop):control+alt+r
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:18.483):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>> IO - speech.speak (08:57:18.539):
>> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
>> IO - speech.speak (08:57:18.680):
>> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
>>
>>
>> Anyway, I'll keep an ear on it.
>> Brian
>> bg...@bl...
>> Sent via blueyonder.
>> Please address personal E-mail to:-
>> br...@bl..., putting 'Brian Gaff'
>> in the display name field.
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvd...@li...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
|
|
From: Brian's M. l. a. B. <bg...@bl...> - 2019-03-11 10:15:19
|
Yes it happened yesterday, but I was time pressed so simply restarted nvda
and it was OK. Of course as I say Sods law dictated it would be in shall we
say an unusual situation today. This was not happening in 2018.1.1.
Brian
bg...@bl...
Sent via blueyonder.
Please address personal E-mail to:-
br...@bl..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Michel Such" <mic...@fr...>
To: "Brian's Mail list account BY via Nvda-devel"
<nvd...@li...>
Sent: Monday, March 11, 2019 10:01 AM
Subject: Re: [Nvda-devel] Possible bug in 2019.1 beta
> Hi,
>
>
> I sometimes notice the same problem, especially in explorer.
>
>
> Michel Such
>
> Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a écrit
> :
>> A kind of lock up happens now and again where only rebooting nvda seems
>> to cure it, but it seems to happen randomly. Sods law being what it is,
>> this mornings happening was in a version of the Outlook Express
>> spellchecker, but yesterday it was in Explorer. As yet I have not been
>> able to test with no add ons or do an nvda/f1, but it looks like the
>> focus stays on an item, wherever it may be and cannot audibly be moved,
>> though it may well move in reality, I could not say at this time. I did
>> do the log for this, and no actual sounding error occurs it just seems to
>> ignore you and repeat.
>> Unfortunately because this one happened in Outlook express nobody will be
>> able to duplicate it, so I'll continue monitoring to see if I can catch
>> it in a more generic place and do the required tests and then do an issue
>> in github if it turns out to be nvda and not an add on.
>>
>> Here is the log I have anyway.
>>
>> IO - inputCore.InputManager.executeGesture (08:56:49.832):
>> Input: kb(desktop):enter
>> IO - speech.speak (08:56:49.948):
>> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
>> Dictionary:\ninagine']
>> IO - speech.speak (08:56:49.950):
>> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
>> IO - speech.speak (08:56:49.950):
>> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.665):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483633: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.667):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.667):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483631: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483592: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.668):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483616: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483593: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.670):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.671):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:51.680):
>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.466):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.473):
>> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
>> childID -2147483613: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.674):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.691):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:54.874):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:54.880):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:56.338):
>> Input: kb(desktop):shift+tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:56:56.346):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483634: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:56:57.665):
>> Input: kb(desktop):downArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:57.788):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:56:58.065):
>> Input: kb(desktop):upArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:58.194):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:56:59.562):
>> Input: kb(desktop):downArrow
>> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:56:59.694):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:00.515):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.526):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483632: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:00.762):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.778):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483644: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.779):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID 0: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.780):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483605: [Error -2147024809] The parameter is incorrect
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:00.782):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:02.072):
>> Input: kb(desktop):tab
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:02.086):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>> IO - inputCore.InputManager.executeGesture (08:57:02.704):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:02.720):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:02.829):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:03.585):
>> Input: kb(desktop):upArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:03.611):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483647: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:03.717):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:09.408):
>> Input: kb(desktop):escape
>> IO - inputCore.InputManager.executeGesture (08:57:10.461):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:10.490):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483646: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:10.596):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:11.844):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:11.862):
>> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
>> childID -2147483640: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:11.969):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:12.329):
>> Input: kb(desktop):downArrow
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:12.348):
>> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
>> childID -2147483614: [Error -2147024809] The parameter is incorrect
>> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
>> Caret didn't move before timeout. Elapsed: 100 ms
>> IO - speech.speak (08:57:12.457):
>> Speaking [LangChangeCommand ('en_GB'), u'imagine']
>> IO - inputCore.InputManager.executeGesture (08:57:18.473):
>> Input: kb(desktop):control+alt+r
>> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
>> (08:57:18.483):
>> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
>> childID -2147483619: [Error -2147024809] The parameter is incorrect
>> IO - speech.speak (08:57:18.539):
>> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
>> IO - speech.speak (08:57:18.680):
>> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
>>
>>
>> Anyway, I'll keep an ear on it.
>> Brian
>> bg...@bl...
>> Sent via blueyonder.
>> Please address personal E-mail to:-
>> br...@bl..., putting 'Brian Gaff'
>> in the display name field.
>>
>>
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvd...@li...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
|
|
From: Michel S. <mic...@fr...> - 2019-03-11 10:02:11
|
Hi,
I sometimes notice the same problem, especially in explorer.
Michel Such
Le 11/03/2019 à 10:57, Brian's Mail list account BY via Nvda-devel a écrit :
> A kind of lock up happens now and again where only rebooting nvda
> seems to cure it, but it seems to happen randomly. Sods law being what
> it is, this mornings happening was in a version of the Outlook Express
> spellchecker, but yesterday it was in Explorer. As yet I have not been
> able to test with no add ons or do an nvda/f1, but it looks like the
> focus stays on an item, wherever it may be and cannot audibly be
> moved, though it may well move in reality, I could not say at this
> time. I did do the log for this, and no actual sounding error occurs
> it just seems to ignore you and repeat.
> Unfortunately because this one happened in Outlook express nobody
> will be able to duplicate it, so I'll continue monitoring to see if I
> can catch it in a more generic place and do the required tests and
> then do an issue in github if it turns out to be nvda and not an add on.
>
> Here is the log I have anyway.
>
> IO - inputCore.InputManager.executeGesture (08:56:49.832):
> Input: kb(desktop):enter
> IO - speech.speak (08:56:49.948):
> Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
> Dictionary:\ninagine']
> IO - speech.speak (08:56:49.950):
> Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
> IO - speech.speak (08:56:49.950):
> Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.665):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483633: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.667):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483634: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.667):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483631: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.668):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483632: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.668):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483592: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.668):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483616: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.670):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483614: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.670):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483593: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.670):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.671):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.680):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.680):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483605: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.680):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483614: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:51.680):
> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
> childID -2147483613: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:56:54.466):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:54.473):
> oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
> childID -2147483613: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:56:54.674):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:54.691):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483634: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:56:54.874):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:54.880):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483632: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:56:56.338):
> Input: kb(desktop):shift+tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:56:56.346):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483634: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:56:57.665):
> Input: kb(desktop):downArrow
> DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:56:57.788):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:56:58.065):
> Input: kb(desktop):upArrow
> DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:56:58.194):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:56:59.562):
> Input: kb(desktop):downArrow
> DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:56:59.694):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:00.515):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.526):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483632: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:57:00.762):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.778):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483644: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.779):
> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.779):
> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.779):
> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
> childID 0: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.780):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483605: [Error -2147024809] The parameter is incorrect
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:00.782):
> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
> childID -2147483619: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:57:02.072):
> Input: kb(desktop):tab
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:02.086):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483647: [Error -2147024809] The parameter is incorrect
> IO - inputCore.InputManager.executeGesture (08:57:02.704):
> Input: kb(desktop):downArrow
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:02.720):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483646: [Error -2147024809] The parameter is incorrect
> DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:57:02.829):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:03.585):
> Input: kb(desktop):upArrow
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:03.611):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483647: [Error -2147024809] The parameter is incorrect
> DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:57:03.717):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:09.408):
> Input: kb(desktop):escape
> IO - inputCore.InputManager.executeGesture (08:57:10.461):
> Input: kb(desktop):downArrow
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:10.490):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483646: [Error -2147024809] The parameter is incorrect
> DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:57:10.596):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:11.844):
> Input: kb(desktop):downArrow
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:11.862):
> oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
> childID -2147483640: [Error -2147024809] The parameter is incorrect
> DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:57:11.969):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:12.329):
> Input: kb(desktop):downArrow
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:12.348):
> oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
> childID -2147483614: [Error -2147024809] The parameter is incorrect
> DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
> Caret didn't move before timeout. Elapsed: 100 ms
> IO - speech.speak (08:57:12.457):
> Speaking [LangChangeCommand ('en_GB'), u'imagine']
> IO - inputCore.InputManager.executeGesture (08:57:18.473):
> Input: kb(desktop):control+alt+r
> DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent
> (08:57:18.483):
> oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
> childID -2147483619: [Error -2147024809] The parameter is incorrect
> IO - speech.speak (08:57:18.539):
> Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
> IO - speech.speak (08:57:18.680):
> Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
>
>
> Anyway, I'll keep an ear on it.
> Brian
> bg...@bl...
> Sent via blueyonder.
> Please address personal E-mail to:-
> br...@bl..., putting 'Brian Gaff'
> in the display name field.
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
|
|
From: Brian's M. l. a. B. <bg...@bl...> - 2019-03-11 09:57:15
|
A kind of lock up happens now and again where only rebooting nvda seems to
cure it, but it seems to happen randomly. Sods law being what it is, this
mornings happening was in a version of the Outlook Express spellchecker, but
yesterday it was in Explorer. As yet I have not been able to test with no
add ons or do an nvda/f1, but it looks like the focus stays on an item,
wherever it may be and cannot audibly be moved, though it may well move in
reality, I could not say at this time. I did do the log for this, and no
actual sounding error occurs it just seems to ignore you and repeat.
Unfortunately because this one happened in Outlook express nobody will be
able to duplicate it, so I'll continue monitoring to see if I can catch it
in a more generic place and do the required tests and then do an issue in
github if it turns out to be nvda and not an add on.
Here is the log I have anyway.
IO - inputCore.InputManager.executeGesture (08:56:49.832):
Input: kb(desktop):enter
IO - speech.speak (08:56:49.948):
Speaking [LangChangeCommand ('en_GB'), u'Spelling dialog Not In
Dictionary:\ninagine']
IO - speech.speak (08:56:49.950):
Speaking [LangChangeCommand ('en_GB'), u'Change To: edit Alt+t']
IO - speech.speak (08:56:49.950):
Speaking [LangChangeCommand ('en_GB'), u'selected imagine']
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.665):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483633: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.667):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483634: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.667):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483631: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.668):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483632: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.668):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483592: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.668):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483616: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.670):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483614: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.670):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483593: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.670):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.671):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.680):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.680):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483605: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.680):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483614: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:51.680):
oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
childID -2147483613: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:56:54.466):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:54.473):
oleacc.AccessibleObjectFromEvent with window 131768, objectID -4 and
childID -2147483613: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:56:54.674):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:54.691):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483634: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:56:54.874):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:54.880):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483632: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:56:56.338):
Input: kb(desktop):shift+tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:56:56.346):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483634: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:56:57.665):
Input: kb(desktop):downArrow
DEBUG - editableText.EditableText._hasCaretMoved (08:56:57.786):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:56:57.788):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:56:58.065):
Input: kb(desktop):upArrow
DEBUG - editableText.EditableText._hasCaretMoved (08:56:58.191):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:56:58.194):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:56:59.562):
Input: kb(desktop):downArrow
DEBUG - editableText.EditableText._hasCaretMoved (08:56:59.691):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:56:59.694):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:00.515):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.526):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483632: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:57:00.762):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.778):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483644: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.779):
oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.779):
oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.779):
oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and childID
0: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.780):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483605: [Error -2147024809] The parameter is incorrect
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:00.782):
oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
childID -2147483619: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:57:02.072):
Input: kb(desktop):tab
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:02.086):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483647: [Error -2147024809] The parameter is incorrect
IO - inputCore.InputManager.executeGesture (08:57:02.704):
Input: kb(desktop):downArrow
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:02.720):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483646: [Error -2147024809] The parameter is incorrect
DEBUG - editableText.EditableText._hasCaretMoved (08:57:02.826):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:57:02.829):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:03.585):
Input: kb(desktop):upArrow
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:03.611):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483647: [Error -2147024809] The parameter is incorrect
DEBUG - editableText.EditableText._hasCaretMoved (08:57:03.714):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:57:03.717):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:09.408):
Input: kb(desktop):escape
IO - inputCore.InputManager.executeGesture (08:57:10.461):
Input: kb(desktop):downArrow
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:10.490):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483646: [Error -2147024809] The parameter is incorrect
DEBUG - editableText.EditableText._hasCaretMoved (08:57:10.594):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:57:10.596):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:11.844):
Input: kb(desktop):downArrow
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:11.862):
oleacc.AccessibleObjectFromEvent with window 197122, objectID -4 and
childID -2147483640: [Error -2147024809] The parameter is incorrect
DEBUG - editableText.EditableText._hasCaretMoved (08:57:11.967):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:57:11.969):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:12.329):
Input: kb(desktop):downArrow
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:12.348):
oleacc.AccessibleObjectFromEvent with window 197232, objectID -4 and
childID -2147483614: [Error -2147024809] The parameter is incorrect
DEBUG - editableText.EditableText._hasCaretMoved (08:57:12.454):
Caret didn't move before timeout. Elapsed: 100 ms
IO - speech.speak (08:57:12.457):
Speaking [LangChangeCommand ('en_GB'), u'imagine']
IO - inputCore.InputManager.executeGesture (08:57:18.473):
Input: kb(desktop):control+alt+r
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (08:57:18.483):
oleacc.AccessibleObjectFromEvent with window 66106, objectID -4 and
childID -2147483619: [Error -2147024809] The parameter is incorrect
IO - speech.speak (08:57:18.539):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
IO - speech.speak (08:57:18.680):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
Anyway, I'll keep an ear on it.
Brian
bg...@bl...
Sent via blueyonder.
Please address personal E-mail to:-
br...@bl..., putting 'Brian Gaff'
in the display name field.
|
|
From: Tony M. <ant...@gm...> - 2019-03-10 21:22:09
|
Yes, in classic browse mode, the same obj.setFocus() is called, see: BrowseModeDocumentTreeInterceptor._set_selection() However, in classic approach the state is not cached immediately; it is cached when focusGained event is received here: BrowseModeDocumentTreeInterceptor.event_gainFocus() In fast browse mode v1 (PR that was reverted by Michael) I tried to receive the same event, only to learn that this way is not reliable - approximately in 0.01% of cases we do not receive focus gain event for some unknown reason. Which is arguably not a big deal in classic browse mode, since every now and then it wouldn't announce that your checkbox was checked or unchecked correctly. I am not even sure that this is happening in classic browse mode - because the bug only appears in 0.01% cases, it is extremely hard to debug. In fast browse mode v1 the manifestation was more severe: buttons wouldn't click if we don't receive focus gained event. In fast browse mode v2 (my current attempt) I am trying to call objsetFocus() and then cache the state immediately without waiting for focusGained event. And yes, you're correct, when we receive stateChanged event, it is fired on another Python object, representing the same checkbox, and I don't understand why this is happening. Best Tony On 3/10/2019 1:40 PM, Felix G. wrote: > Hi, > so in fast browse mode you call obj.setFocus() and then cache the > properties, only to find that the state change fires for another > Python object representing the same control. In contrast, how is focus > set in the classic approach when the user moves in the virtual buffer? > Is that also an obj.setFocus()? > Best, > Felix > > Am So., 10. März 2019 um 11:07 Uhr schrieb Brians old account via > Nvda-devel <nvd...@li...>: >> Not being a programmer of Python, feel free to throw this under the wheels >> of the next passing programmer vehicle, but you mention one value being >> integer and the other not, When only one is created in the old system is it >> int or not? That might point you at where the extra one is coming from due >> to integer either being forced or one assumes something else resulting >> from the calculation so it goes back and creates another object. >> Brian >> >> bg...@li... >> Brian Gaff's other account. >> >> ----- Original Message ----- >> From: "Tony Malykh" <ant...@gm...> >> To: <nvd...@li...> >> Sent: Saturday, March 09, 2019 10:49 PM >> Subject: [Nvda-devel] Problem with fast browse mode - multiple NVDAObjects >> are created >> >> >>> Hello NVDA devs and especially Michael, >>> >>> I am trying to work on fast browse mode PR (a.k.a. focus follows browse >>> mode off). >>> Just a quick recap: In v1 of this PR there were some bugs related to the >>> fact that some logic was asynchronous and it relied on gainFocus event >>> being received from the operating system. However in some cases for >>> unknown reason operating system wouldn't send this event, causing bugs >>> that are hard to deal with, such as inability to activate form elements on >>> web pages. >>> I am now working on v2: >>> https://github.com/nvaccess/nvda/pull/9360 >>> The code is by no means ready to be reviewed, but it's just for the >>> reference. >>> The main change in v2 is replacing asynchronous logic with synchronous >>> logic there, and in general it works, but there is one new bugI'm facing >>> that I would like to discuss and maybe ask for some help. >>> >>> Basic description of the bug: >>> When unchecking a checkbox on a web page, its new state is not being >>> announced. The bug only reproduces for unchecking - that is checking >>> previously blank checkbox works as expected. >>> Here are the concrete steps to reproduce the bug. >>> 1. Enter Fast browse mode by pressing NVDA+num row 8. >>> 2. In Chrome or Firefox navigate to >>> https://www.ironspider.ca/forms/checkradio.htm >>> 3. Check the first 3 checkboxes on the page >>> 4. Go back to the first check box >>> 5. Press space to uncheck it. The check box will be successfully >>> unchecked, but the new state will not be announced immediately. >>> >>> I spent some time debugging this , and here are my findings so far. >>> Announcing state change works like this. First >>> speech.speakObject(obj,controlTypes.REASON_ONLYCACHE) is called to cache >>> the previous state. In traditional browse mode this function is called >>> when user navigates to that checkbox, and therefore system focus is >>> switched to that checkbox as well. This happens in >>> BrowseModeDocumentTreeInterceptor.event_gainFocus. >>> Then, assuming that user presses space bar on a checkbox, >>> BrowseModeTreeInterceptor._activatePosition is triggered, which activates >>> this checkbox. Shortly, in response to that we receive a state changed >>> event, that is processed in NVDAObject.event_stateChange(), which in turn >>> calls speech.speakObjectProperties(self,states=True, >>> reason=controlTypes.REASON_CHANGE). >>> So we make two calls to speech module: the first one to cache object >>> properties, the second one to speak whatever properties have changed. >>> Cached properties are stored inside NVDAObject, so it is very important >>> that the same object is passed to both these calls. >>> >>> Now back to fast browse mode v2. Since we don't update system focus on >>> every browse mode focus change, we need to update system focus right >>> before activating the checkbox. This is accomplished in >>> BrowseModeTreeInterceptor.maybeSyncFocus(). And in the same function, >>> right after I call obj.setFocus(), I also call >>> speech.speakObject(obj,controlTypes.REASON_ONLYCACHE). >>> However, here is the problem. When we receive state changed event, the >>> function NVDAObject.event_stateChange is called on a different NVDA object >>> instance. So we completely miss the cached state. >>> When I say a different NVDAObject instance, I only mean a different python >>> object. So there are apparently (at least) two NVDAObjects, I'll call them >>> NVDAObject1 and NVDAObject2. Both represent the same checkbox in the >>> browser, both have the same IA2UniqueID and windowHandle. Yet in the first >>> call (cacheonly) I see NVDAObject1, and the state changed event comes in >>> with NVDAObject2. >>> To illustrate this, here is the example from my logs (slightly formatted): >>> cacheonly from maybeSyncFocus(): >>> <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A370> >>> uniqueID = (67548, -33555216) >>> speakObject on stateChanged >>> <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A1F0> >>> uniqueID = (67548L, -33555216) >>> >>> So the big question I have is why there are two separate NVDAObjects >>> created for the same checkbox in my scenario? And why they are not created >>> Without my PR? What is logic behind creating new NVDA Objects? I did some >>> cursory debugging of that and I saw that most of NVDAObjects are created >>> using function getNVDAObjectFromEvent() defined in >>> IAccessible2\__init__.py, and there doesn't seem to be any caching logic >>> there. >>> It seems there are two potential approaches of tackling this issue. >>> 1. We need to figure out why two separate NVDA objects are created. >>> 2. Potentially another approach is to allow creating multiple python >>> NVDAObjects for the same Checkbox (or any other real IAccessible2 object), >>> and have a properties cache that would take this into account. Some kind >>> of weakKeyDictionary might work. Property caching logic in speech.py might >>> have to be redesigned though. >>> >>> And also another thing worth noticing in the logs that I pasted above. >>> UniqueID is a tuple of WindowHandle and IA2UniqueID . If you looked at >>> both entries carefully, you would notice that WindowHandle is slightly >>> different: even though the value is the same, in the first entry it is >>> int, and in the second entry it is long. This looks very suspicious to me. >>> Do you think this might be the reason why two copies of NVDAObjects are >>> created? On the other hand it doesn't explain why two objects are not >>> created in stock NVDA. >>> >>> Anyway, this is current state of my second attempt to implement fast >>> browse mode. Any suggestions will be appreciated! >>> Best >>> --Tony >>> >>> >>> >>> _______________________________________________ >>> Nvda-devel mailing list >>> Nvd...@li... >>> https://lists.sourceforge.net/lists/listinfo/nvda-devel >>> >> >> >> _______________________________________________ >> Nvda-devel mailing list >> Nvd...@li... >> https://lists.sourceforge.net/lists/listinfo/nvda-devel > > _______________________________________________ > Nvda-devel mailing list > Nvd...@li... > https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Felix G. <con...@gm...> - 2019-03-10 20:41:16
|
Hi, so in fast browse mode you call obj.setFocus() and then cache the properties, only to find that the state change fires for another Python object representing the same control. In contrast, how is focus set in the classic approach when the user moves in the virtual buffer? Is that also an obj.setFocus()? Best, Felix Am So., 10. März 2019 um 11:07 Uhr schrieb Brians old account via Nvda-devel <nvd...@li...>: > > Not being a programmer of Python, feel free to throw this under the wheels > of the next passing programmer vehicle, but you mention one value being > integer and the other not, When only one is created in the old system is it > int or not? That might point you at where the extra one is coming from due > to integer either being forced or one assumes something else resulting > from the calculation so it goes back and creates another object. > Brian > > bg...@li... > Brian Gaff's other account. > > ----- Original Message ----- > From: "Tony Malykh" <ant...@gm...> > To: <nvd...@li...> > Sent: Saturday, March 09, 2019 10:49 PM > Subject: [Nvda-devel] Problem with fast browse mode - multiple NVDAObjects > are created > > > > Hello NVDA devs and especially Michael, > > > > I am trying to work on fast browse mode PR (a.k.a. focus follows browse > > mode off). > > Just a quick recap: In v1 of this PR there were some bugs related to the > > fact that some logic was asynchronous and it relied on gainFocus event > > being received from the operating system. However in some cases for > > unknown reason operating system wouldn't send this event, causing bugs > > that are hard to deal with, such as inability to activate form elements on > > web pages. > > I am now working on v2: > > https://github.com/nvaccess/nvda/pull/9360 > > The code is by no means ready to be reviewed, but it's just for the > > reference. > > The main change in v2 is replacing asynchronous logic with synchronous > > logic there, and in general it works, but there is one new bugI'm facing > > that I would like to discuss and maybe ask for some help. > > > > Basic description of the bug: > > When unchecking a checkbox on a web page, its new state is not being > > announced. The bug only reproduces for unchecking - that is checking > > previously blank checkbox works as expected. > > Here are the concrete steps to reproduce the bug. > > 1. Enter Fast browse mode by pressing NVDA+num row 8. > > 2. In Chrome or Firefox navigate to > > https://www.ironspider.ca/forms/checkradio.htm > > 3. Check the first 3 checkboxes on the page > > 4. Go back to the first check box > > 5. Press space to uncheck it. The check box will be successfully > > unchecked, but the new state will not be announced immediately. > > > > I spent some time debugging this , and here are my findings so far. > > Announcing state change works like this. First > > speech.speakObject(obj,controlTypes.REASON_ONLYCACHE) is called to cache > > the previous state. In traditional browse mode this function is called > > when user navigates to that checkbox, and therefore system focus is > > switched to that checkbox as well. This happens in > > BrowseModeDocumentTreeInterceptor.event_gainFocus. > > Then, assuming that user presses space bar on a checkbox, > > BrowseModeTreeInterceptor._activatePosition is triggered, which activates > > this checkbox. Shortly, in response to that we receive a state changed > > event, that is processed in NVDAObject.event_stateChange(), which in turn > > calls speech.speakObjectProperties(self,states=True, > > reason=controlTypes.REASON_CHANGE). > > So we make two calls to speech module: the first one to cache object > > properties, the second one to speak whatever properties have changed. > > Cached properties are stored inside NVDAObject, so it is very important > > that the same object is passed to both these calls. > > > > Now back to fast browse mode v2. Since we don't update system focus on > > every browse mode focus change, we need to update system focus right > > before activating the checkbox. This is accomplished in > > BrowseModeTreeInterceptor.maybeSyncFocus(). And in the same function, > > right after I call obj.setFocus(), I also call > > speech.speakObject(obj,controlTypes.REASON_ONLYCACHE). > > However, here is the problem. When we receive state changed event, the > > function NVDAObject.event_stateChange is called on a different NVDA object > > instance. So we completely miss the cached state. > > When I say a different NVDAObject instance, I only mean a different python > > object. So there are apparently (at least) two NVDAObjects, I'll call them > > NVDAObject1 and NVDAObject2. Both represent the same checkbox in the > > browser, both have the same IA2UniqueID and windowHandle. Yet in the first > > call (cacheonly) I see NVDAObject1, and the state changed event comes in > > with NVDAObject2. > > To illustrate this, here is the example from my logs (slightly formatted): > > cacheonly from maybeSyncFocus(): > > <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A370> > > uniqueID = (67548, -33555216) > > speakObject on stateChanged > > <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A1F0> > > uniqueID = (67548L, -33555216) > > > > So the big question I have is why there are two separate NVDAObjects > > created for the same checkbox in my scenario? And why they are not created > > Without my PR? What is logic behind creating new NVDA Objects? I did some > > cursory debugging of that and I saw that most of NVDAObjects are created > > using function getNVDAObjectFromEvent() defined in > > IAccessible2\__init__.py, and there doesn't seem to be any caching logic > > there. > > It seems there are two potential approaches of tackling this issue. > > 1. We need to figure out why two separate NVDA objects are created. > > 2. Potentially another approach is to allow creating multiple python > > NVDAObjects for the same Checkbox (or any other real IAccessible2 object), > > and have a properties cache that would take this into account. Some kind > > of weakKeyDictionary might work. Property caching logic in speech.py might > > have to be redesigned though. > > > > And also another thing worth noticing in the logs that I pasted above. > > UniqueID is a tuple of WindowHandle and IA2UniqueID . If you looked at > > both entries carefully, you would notice that WindowHandle is slightly > > different: even though the value is the same, in the first entry it is > > int, and in the second entry it is long. This looks very suspicious to me. > > Do you think this might be the reason why two copies of NVDAObjects are > > created? On the other hand it doesn't explain why two objects are not > > created in stock NVDA. > > > > Anyway, this is current state of my second attempt to implement fast > > browse mode. Any suggestions will be appreciated! > > Best > > --Tony > > > > > > > > _______________________________________________ > > Nvda-devel mailing list > > Nvd...@li... > > https://lists.sourceforge.net/lists/listinfo/nvda-devel > > > > > > _______________________________________________ > Nvda-devel mailing list > Nvd...@li... > https://lists.sourceforge.net/lists/listinfo/nvda-devel |
|
From: Brians o. a. <bg...@bl...> - 2019-03-10 10:07:18
|
Not being a programmer of Python, feel free to throw this under the wheels of the next passing programmer vehicle, but you mention one value being integer and the other not, When only one is created in the old system is it int or not? That might point you at where the extra one is coming from due to integer either being forced or one assumes something else resulting from the calculation so it goes back and creates another object. Brian bg...@li... Brian Gaff's other account. ----- Original Message ----- From: "Tony Malykh" <ant...@gm...> To: <nvd...@li...> Sent: Saturday, March 09, 2019 10:49 PM Subject: [Nvda-devel] Problem with fast browse mode - multiple NVDAObjects are created > Hello NVDA devs and especially Michael, > > I am trying to work on fast browse mode PR (a.k.a. focus follows browse > mode off). > Just a quick recap: In v1 of this PR there were some bugs related to the > fact that some logic was asynchronous and it relied on gainFocus event > being received from the operating system. However in some cases for > unknown reason operating system wouldn't send this event, causing bugs > that are hard to deal with, such as inability to activate form elements on > web pages. > I am now working on v2: > https://github.com/nvaccess/nvda/pull/9360 > The code is by no means ready to be reviewed, but it's just for the > reference. > The main change in v2 is replacing asynchronous logic with synchronous > logic there, and in general it works, but there is one new bugI'm facing > that I would like to discuss and maybe ask for some help. > > Basic description of the bug: > When unchecking a checkbox on a web page, its new state is not being > announced. The bug only reproduces for unchecking - that is checking > previously blank checkbox works as expected. > Here are the concrete steps to reproduce the bug. > 1. Enter Fast browse mode by pressing NVDA+num row 8. > 2. In Chrome or Firefox navigate to > https://www.ironspider.ca/forms/checkradio.htm > 3. Check the first 3 checkboxes on the page > 4. Go back to the first check box > 5. Press space to uncheck it. The check box will be successfully > unchecked, but the new state will not be announced immediately. > > I spent some time debugging this , and here are my findings so far. > Announcing state change works like this. First > speech.speakObject(obj,controlTypes.REASON_ONLYCACHE) is called to cache > the previous state. In traditional browse mode this function is called > when user navigates to that checkbox, and therefore system focus is > switched to that checkbox as well. This happens in > BrowseModeDocumentTreeInterceptor.event_gainFocus. > Then, assuming that user presses space bar on a checkbox, > BrowseModeTreeInterceptor._activatePosition is triggered, which activates > this checkbox. Shortly, in response to that we receive a state changed > event, that is processed in NVDAObject.event_stateChange(), which in turn > calls speech.speakObjectProperties(self,states=True, > reason=controlTypes.REASON_CHANGE). > So we make two calls to speech module: the first one to cache object > properties, the second one to speak whatever properties have changed. > Cached properties are stored inside NVDAObject, so it is very important > that the same object is passed to both these calls. > > Now back to fast browse mode v2. Since we don't update system focus on > every browse mode focus change, we need to update system focus right > before activating the checkbox. This is accomplished in > BrowseModeTreeInterceptor.maybeSyncFocus(). And in the same function, > right after I call obj.setFocus(), I also call > speech.speakObject(obj,controlTypes.REASON_ONLYCACHE). > However, here is the problem. When we receive state changed event, the > function NVDAObject.event_stateChange is called on a different NVDA object > instance. So we completely miss the cached state. > When I say a different NVDAObject instance, I only mean a different python > object. So there are apparently (at least) two NVDAObjects, I'll call them > NVDAObject1 and NVDAObject2. Both represent the same checkbox in the > browser, both have the same IA2UniqueID and windowHandle. Yet in the first > call (cacheonly) I see NVDAObject1, and the state changed event comes in > with NVDAObject2. > To illustrate this, here is the example from my logs (slightly formatted): > cacheonly from maybeSyncFocus(): > <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A370> > uniqueID = (67548, -33555216) > speakObject on stateChanged > <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A1F0> > uniqueID = (67548L, -33555216) > > So the big question I have is why there are two separate NVDAObjects > created for the same checkbox in my scenario? And why they are not created > Without my PR? What is logic behind creating new NVDA Objects? I did some > cursory debugging of that and I saw that most of NVDAObjects are created > using function getNVDAObjectFromEvent() defined in > IAccessible2\__init__.py, and there doesn't seem to be any caching logic > there. > It seems there are two potential approaches of tackling this issue. > 1. We need to figure out why two separate NVDA objects are created. > 2. Potentially another approach is to allow creating multiple python > NVDAObjects for the same Checkbox (or any other real IAccessible2 object), > and have a properties cache that would take this into account. Some kind > of weakKeyDictionary might work. Property caching logic in speech.py might > have to be redesigned though. > > And also another thing worth noticing in the logs that I pasted above. > UniqueID is a tuple of WindowHandle and IA2UniqueID . If you looked at > both entries carefully, you would notice that WindowHandle is slightly > different: even though the value is the same, in the first entry it is > int, and in the second entry it is long. This looks very suspicious to me. > Do you think this might be the reason why two copies of NVDAObjects are > created? On the other hand it doesn't explain why two objects are not > created in stock NVDA. > > Anyway, this is current state of my second attempt to implement fast > browse mode. Any suggestions will be appreciated! > Best > --Tony > > > > _______________________________________________ > Nvda-devel mailing list > Nvd...@li... > https://lists.sourceforge.net/lists/listinfo/nvda-devel > |
|
From: Tony M. <ant...@gm...> - 2019-03-09 22:49:28
|
Hello NVDA devs and especially Michael, I am trying to work on fast browse mode PR (a.k.a. focus follows browse mode off). Just a quick recap: In v1 of this PR there were some bugs related to the fact that some logic was asynchronous and it relied on gainFocus event being received from the operating system. However in some cases for unknown reason operating system wouldn't send this event, causing bugs that are hard to deal with, such as inability to activate form elements on web pages. I am now working on v2: https://github.com/nvaccess/nvda/pull/9360 The code is by no means ready to be reviewed, but it's just for the reference. The main change in v2 is replacing asynchronous logic with synchronous logic there, and in general it works, but there is one new bugI'm facing that I would like to discuss and maybe ask for some help. Basic description of the bug: When unchecking a checkbox on a web page, its new state is not being announced. The bug only reproduces for unchecking - that is checking previously blank checkbox works as expected. Here are the concrete steps to reproduce the bug. 1. Enter Fast browse mode by pressing NVDA+num row 8. 2. In Chrome or Firefox navigate to https://www.ironspider.ca/forms/checkradio.htm 3. Check the first 3 checkboxes on the page 4. Go back to the first check box 5. Press space to uncheck it. The check box will be successfully unchecked, but the new state will not be announced immediately. I spent some time debugging this , and here are my findings so far. Announcing state change works like this. First speech.speakObject(obj,controlTypes.REASON_ONLYCACHE) is called to cache the previous state. In traditional browse mode this function is called when user navigates to that checkbox, and therefore system focus is switched to that checkbox as well. This happens in BrowseModeDocumentTreeInterceptor.event_gainFocus. Then, assuming that user presses space bar on a checkbox, BrowseModeTreeInterceptor._activatePosition is triggered, which activates this checkbox. Shortly, in response to that we receive a state changed event, that is processed in NVDAObject.event_stateChange(), which in turn calls speech.speakObjectProperties(self,states=True, reason=controlTypes.REASON_CHANGE). So we make two calls to speech module: the first one to cache object properties, the second one to speak whatever properties have changed. Cached properties are stored inside NVDAObject, so it is very important that the same object is passed to both these calls. Now back to fast browse mode v2. Since we don't update system focus on every browse mode focus change, we need to update system focus right before activating the checkbox. This is accomplished in BrowseModeTreeInterceptor.maybeSyncFocus(). And in the same function, right after I call obj.setFocus(), I also call speech.speakObject(obj,controlTypes.REASON_ONLYCACHE). However, here is the problem. When we receive state changed event, the function NVDAObject.event_stateChange is called on a different NVDA object instance. So we completely miss the cached state. When I say a different NVDAObject instance, I only mean a different python object. So there are apparently (at least) two NVDAObjects, I'll call them NVDAObject1 and NVDAObject2. Both represent the same checkbox in the browser, both have the same IA2UniqueID and windowHandle. Yet in the first call (cacheonly) I see NVDAObject1, and the state changed event comes in with NVDAObject2. To illustrate this, here is the example from my logs (slightly formatted): cacheonly from maybeSyncFocus(): <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A370> uniqueID = (67548, -33555216) speakObject on stateChanged <NVDAObjects.IAccessible.mozilla.Mozilla object at 0x07A6A1F0> uniqueID = (67548L, -33555216) So the big question I have is why there are two separate NVDAObjects created for the same checkbox in my scenario? And why they are not created Without my PR? What is logic behind creating new NVDA Objects? I did some cursory debugging of that and I saw that most of NVDAObjects are created using function getNVDAObjectFromEvent() defined in IAccessible2\__init__.py, and there doesn't seem to be any caching logic there. It seems there are two potential approaches of tackling this issue. 1. We need to figure out why two separate NVDA objects are created. 2. Potentially another approach is to allow creating multiple python NVDAObjects for the same Checkbox (or any other real IAccessible2 object), and have a properties cache that would take this into account. Some kind of weakKeyDictionary might work. Property caching logic in speech.py might have to be redesigned though. And also another thing worth noticing in the logs that I pasted above. UniqueID is a tuple of WindowHandle and IA2UniqueID . If you looked at both entries carefully, you would notice that WindowHandle is slightly different: even though the value is the same, in the first entry it is int, and in the second entry it is long. This looks very suspicious to me. Do you think this might be the reason why two copies of NVDAObjects are created? On the other hand it doesn't explain why two objects are not created in stock NVDA. Anyway, this is current state of my second attempt to implement fast browse mode. Any suggestions will be appreciated! Best --Tony |
|
From: Abdel <abd...@fr...> - 2019-03-07 08:55:03
|
Hi,
Larry:
Thank you so much for your answer.
I also found this in a reply posted by Leonard.
> https://sourceforge.net/p/nvda/lists/message/36493189/
Here is the recommended syntax:
> from six import with_metaclass
> import abc
>
> class MyAbstractClass (with_metaclass (abc.ABCMeta, object)):
>
> @abc.abstractmethod
> def myAbstractMethod (self):
> pass
Thanks again.
Cheers,
Abdel.
Le 06/03/2019 à 12:18, Larry Wang a écrit :
>
> Hi,
>
>
> Abdel
>
> This problem has been discussed in a previous issue.
>
> https://github.com/nvaccess/nvda/issues/8652
>
> Examples can be found there.
>
> fromsix importwith_metaclass
>
> classNVDAObject(with_metaclass(DynamicNVDAObjectType,
> documentBase.TextContainerObject,baseObject.ScriptableObject))
>
>
>
>
> On Tue, Mar 5, 2019 at 11:20 PM Abdel <abd...@fr...
> <mailto:abd...@fr...>> wrote:
>
> Hi,
>
> I'm trying to use abstract classes in a module.
>
> The problem I encounter is the following:
>
> I would like to use the abc.ABC class found in Python 3, with
> Python 2.7.
>
> The problem is that this class abc.ABC is not available with
> Python 2.7.
>
> To be able to use Python 2.7 and 3 compatible code, I had to use
> the following syntax:
>
>> import abc
>>
>> ABC = abc.ABC if hasattr (abc, 'ABC') else abc.ABCMeta ('ABC',
>> (object,), {'__slots__': ()})
>>
>> class MyAbstractClass (ABC):
>>
>> @abc.abstractmethod
>> def myAbstractMethod (self):
>> pass
>
>
> For testing :
>
>
>> MyAbstractClass ()
>
>
> Result :
>
>
>> Traceback (most recent call last):
>> File "<console>", line 1, in <module>
>> TypeError: Can't instantiate abstract class MyAbstractClass with
>> abstract methods myAbstractMethod
>
>
> Of course, this is the expected behavior.
>
>
> Question :
>
>
> Is there a simpler syntax to get the same result, i.e. use the
> abc.ABC class with Python 2.7 and 3?
>
> Thanks in advance for your answers.
>
> Kind regards,
> Abdel.
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> <mailto:Nvd...@li...>
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>
>
>
>
>
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
|
|
From: Larry W. <lar...@gm...> - 2019-03-06 11:19:00
|
Hi, Abdel This problem has been discussed in a previous issue. https://github.com/nvaccess/nvda/issues/8652 Examples can be found there. from six import with_metaclass class NVDAObject(with_metaclass(DynamicNVDAObjectType, documentBase.TextContainerObject,baseObject.ScriptableObject)) On Tue, Mar 5, 2019 at 11:20 PM Abdel <abd...@fr...> wrote: > Hi, > > I'm trying to use abstract classes in a module. > > The problem I encounter is the following: > > I would like to use the abc.ABC class found in Python 3, with Python 2.7. > > The problem is that this class abc.ABC is not available with Python 2.7. > > To be able to use Python 2.7 and 3 compatible code, I had to use the > following syntax: > > import abc > > ABC = abc.ABC if hasattr (abc, 'ABC') else abc.ABCMeta ('ABC', (object,), > {'__slots__': ()}) > > class MyAbstractClass (ABC): > > @abc.abstractmethod > def myAbstractMethod (self): > pass > > > > For testing : > > > MyAbstractClass () > > > > Result : > > > Traceback (most recent call last): > File "<console>", line 1, in <module> > TypeError: Can't instantiate abstract class MyAbstractClass with abstract > methods myAbstractMethod > > > > Of course, this is the expected behavior. > > Question : > > > Is there a simpler syntax to get the same result, i.e. use the abc.ABC > class with Python 2.7 and 3? > > Thanks in advance for your answers. > > Kind regards, > Abdel. > _______________________________________________ > Nvda-devel mailing list > Nvd...@li... > https://lists.sourceforge.net/lists/listinfo/nvda-devel > |
171 messages has been excluded from this view by a project administrator.
