[nvda] Implication of a change

For those of us not intimate with windows processes, can someone explain this entry in the change log?
UIAHandler: do not allow events, or interaction with UIA elements, coming from NVDA's process. Due to limitations in the Windows UIA implementation, doing so would cause freezes. Specifically this seems to fix a freeze when going to Save As in NVDA's log viewer. This does mean though that dialogs such as that Save as dialog will only be accessible via MSAA, no UIA features can work there.
Not really sure of the implications, as I do not know what the processes might be that were in use so to speak. 

Brian
Brian Gaff bglists@xxxxxxxxxxxxxxxxx If you need to email me please send it to 
briang1@xxxxxxxxxxxxxxxx
Making sure the name 'Brian Gaff' is in the display name field.
Failure to do this may result in delays or message loss.
Some sacrifices are a fact of life in our junk mail riddled world! 

To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts:

  • » [nvda] Implication of a change - brian gafff \(Line One\)