[nvda] A few quite interesting behaviours with nvda

Hey all.
I have a few very interesting observations with the latest 2300 snapshot and i saw them in the earlier snapshots so i'd like to check if the rest of the people have the same issues, or if it could be fixed somehow, or something is wrong with my system. 1. When i use miranda messenger, if i focus to the output window with all written and incoming messages, if i scroll with and arrow keys to read the messages, when ever the message is read, after that nvda starts to deselect all the text from the window and it starts to read its content from top to bottom of the window. Does anyone has a clew what's going on? 2. I have ms office 2003 sp3, and if i read the text in ms word and i stop the cursor with ctrl key, the cursor doesn't stop on the position where i stopped it, instead the cursor is somewhere on the beginning of the current page of the document, and sometimes even on the previous page, so i can't find out where i stopped the reading of the document. Is there the way how to solve this problem or does anyone has a clew what could cause this kind of behaviour? I'm also looking for a solution of putting the bookmark or placemarker or something in the document so that i can start reading where i stopped last time if the document is closed in the mean time. 3. If i'm in the windows explorer or my computer, and for exampel i want to rename the file name, if i press f2 to change the name of the file, when i move thru the file name with left and right arrow keys, first what i hear is "unselected". So it looks like that whole file name is selected and if i move with the arrows it becomes unselected. 4. When i'm in the excel 2003 and when i scroll thru the data sheet with and arrow keys, nvda is reading their contents but if i try to edit the sheet with f2 and copy its content, nvda doesn't anounce anything. The same is if i scroll thru the data sheet with tab or shift tab keys, nvda stays quiet. Also, if the cell has written comment, nvda doesn't anounce it at all, but the other screen reader can identify it. Ok that could be the issue with MSAA but anyway, very interesting behaviour, because if i'm correct that worked before and i could edit the cells and read what's inside without problems. 
I'm attaching my log file if it could help.
Regards
mario

Other related posts: