Regrettably, I have similar problems. I had to go back and install the previous JAWS version to be able to review this email thread and be allowed to use the enter key to get into this email message and respond to this problem.
I will be writing a note to the Freedom Scientific technical support team and hope they may be able to help out. Larry Marcotte correctly pronounced as Larry Marcaught -----Original Message----- From: Jfw [mailto:[email protected]] On Behalf Of Paul Martz via Jfw Sent: Thursday, October 15, 2015 2:16 PM To: 'The Jaws for Windows support list.' Cc: Paul Martz Subject: RE: Problem with New JAWS v16.0.4463 and Outlook 2010 Thanks for everyone's continued help with this issue. It is not a problem with the Outlook window being minimized. The behavior is the same whether the window is maximized or "restored". I also played around with the "Customize Outlook Message List" JAWS manager, a very cool little tool that I hadn't heard of before, and again no luck. Regardless of how I configured this, I still got the same incorrect behavior. But I finally figured out a workaround. In the "View" tab of the ribbon UI, I have to uncheck "Show as Conversation". Once I do that, everything reads correctly. But if I have that checked, then nothing is read as I arrow down through my message list. This is not an ideal workaround, as I rather like to have messages grouped by conversation, but at least I can access my email again. I guess my next thing to try would be to completely uninstall JAWS including my own custom settings, then reinstall, and see if that resolves this issue. After all, no one else is encountering this problem, so it must be something specific to my system. Thanks, all. I consider this closed, and J Bron can go ahead and hijack this thread now if he wants to. <grin> -Paul > -----Original Message----- > Paul, > > This behavior reminds me of the times I've somehow minimalized Outlook > 2010. If this is the problem, the solution is to focus on the Outlook window, > press alt-space, then x for maximize. > > For what it's worth, even though the problem arose after installation > of a JAWS update and this action apparently caused the change, it > doesn't sound like a JAWS issue. _______________________________________________ Jfw mailing list [email protected] http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com _______________________________________________ Jfw mailing list [email protected] http://lists.the-jdh.com/mailman/listinfo/jfw_lists.the-jdh.com
