You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I saw that UIA is a bit slow than other screen readers (in stable releases), but after some testing I saw a better performance with this version of comtypes, not so much, but it is notable.
Describe the solution you'd like
I don't know what should be the correct solution, because a comment from @LeonarddeR on #8522. I was searching for the particular bug and I didn't found anything.
Describe alternatives you've considered
I whas thinking about NVDA object caching, primarily for UIAHandler because it has a bad performance, same to JABHandler. I'm planning to do some testing today.
Additional context
I saw in UIAHandler that every time that an event ocurs a new object is created. I suppose that it takes some time to instantiate it, and it impacts to NVDA's performance in heavy UIAutomation applications, such Visual Studio.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I saw that UIA is a bit slow than other screen readers (in stable releases), but after some testing I saw a better performance with this version of comtypes, not so much, but it is notable.
Describe the solution you'd like
I don't know what should be the correct solution, because a comment from @LeonarddeR on #8522. I was searching for the particular bug and I didn't found anything.
Describe alternatives you've considered
I whas thinking about NVDA object caching, primarily for UIAHandler because it has a bad performance, same to JABHandler. I'm planning to do some testing today.
Additional context
I saw in UIAHandler that every time that an event ocurs a new object is created. I suppose that it takes some time to instantiate it, and it impacts to NVDA's performance in heavy UIAutomation applications, such Visual Studio.
The text was updated successfully, but these errors were encountered: