Hi: I just caused we to lock up when not suppose to. In the "dead spot" I routed the mouse to the cursor and up and down arrowed, num keypad. The mouse read the text in the text editer correctly indicating the cursor is, or should be, in the text editer since I routed the mouse to it. When the Error List is up correctly and I route the mouse to the cursor the mouse reads the error messages in the ErrorList Window and is not reading the text in the text editer so the mouse seems to handle things correctly in this particular case. This may indicate a disjoint between what WE is reading and what is under the cursor and the mouse when routed to the cursor. Any ideas of what WE looks for on inverted t up and down arrow to read if not based on what is under the cursor? I do see where there are squiggles being added to the error text I think but would that lock WE so down arrow would not progress to subsequent lines in the Editer? Rick USA
_______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
