About the mannual, lots of people are not aware that searching a chm file i.e. the WE mannual is a compiled html help document, is very simple. Open the mannual from the WE Helps menu and type Alt plus S and type the word to search and after you enter type Alt plus T.
You can read the mannual sequentially or search it and read the relevant portions. Hope this helps. Regards Jitendra -----Original Message----- From: Aaron Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 8:42 PM To: Michael D. Lawler Subject: Re: how to know when a setting will be changed globally or per set file. James, You said: "By contrast, when I went to the knowledgebase and started reading some of Arron's [sic] articles and saw how logically they were written, I was very excited, because I started picking up concepts more quickly." I guess now would be a bad time to point out that I write the manual too, huh? <grin> Actually, the manual was written by several people over time, and I agree that it could stand some updating in terms of it's layout. On the other hand, for as many people who are unsuccessful with the manual, we have the same number who tell us how invaluable it has been, how it reads just like a tutorial, and how easy it is for them to find information in it. Writing technical documentation that's accessible to everyone is impossible. We do try, however, to make concepts easy to understand. Sometimes we succeed, sometimes we don't. What's important is your feedback so that we know which sections need massaging, and so we know which sections do work for you. With that knowledge, we can compare and contrast the documentation, beefing up those places that are lacking. In the past, it was difficult to make a lot of changes to the documentation because of all the various formats that had to be updated. We're in the process of re-thinking the ways that we make documentation available, and we'll be able to update more of the manual more often when all of that gets finalized. Thanks for the input. Aaron >> Subject: Re: how to know when a setting will be changed globally or >> per set file. >> To: [email protected] >> From: [EMAIL PROTECTED] >> >> Hi, >> This is my feeling too. Please don't take this the wrong way, but the >> manual is very confusing for me to read. I think that it is one of >> WE's weaknesses. >> >> Reading the manual is one of the most frustrating aspects of learning >> WE for me. You have to go all the way to chapter 8 before you start >> learning key strokes for reading. Then, once you get there, the title >> of 8.3 is Reading characters, words, sentences and paragraphs. Once >> you start reading the content, you get this verbose explanation about >> what happens when you leave your computer. Then it starts talking >> about how to read by sentence rather than how to read by character. >> You don't get to see how to read by paragraph until you see the list >> of factory keys. I don't think that list should be there at all >> because it distracts me. It starts making me curious about what >> character after and sentence before mean. Then I wonder if some how >> that's important to what I'm trying to learn. >> >> This chapter is an example of one of the fundamental differences in >> the reading philosophies between JAWS and Window-eyes, and because it >> is laid out the way it is, it's easy to miss the point that it's so >> easy to look around without having to move your cursor, which is one >> of Window-Eye's strengths. >> >> I would want the text to come in the order the title states it will >> be in. >> That would be an aid to learning. Tell us how to read by characters, >> words, sentences, and paragraphs just as the title states. Either >> save the other stuff for the end of the chapter or have a See also >> section that refers us to other parts of the manual. The extra >> details are confusing to me. >> >> By contrast, when I went to the knowledgebase and started reading >> some of Arron's articles and saw how logically they were written, I >> was very excited, because I started picking up concepts more quickly. >> The articles were very logically laid out and written in a much more >> step-by-step fashion. They didn't go off on so many tangents. Side >> notes were mostly at the bottom, after the main points of the >> articles were explained. >> >> Thanks for considering these points. >> >> Jim >> James D Homme, Usability Engineering, Highmark Inc., >> [EMAIL PROTECTED], 412-544-1810 >> >> "The difference between those who get what they wish for and those >> who don't is action. Therefore, every action you take is a complete >> success,regardless of the results." -- Jerrold Mundis Highmark >> internal only: For usability and accessibility: >> http://highwire.highmark.com/sites/iwov/hwt093/ >> >> >> >> [EMAIL PROTECTED] >> .net >> >> To >> 08/21/2008 09:44 [email protected] >> >> AM cc >> >> >> Subject >> Please respond to how to know when a setting will be >> [EMAIL PROTECTED] changed globally or per set file. >> .net >> >> >> >> >> >> >> >> >> >> Good Morning, >> >> I have been using Window-Eyes almost exclusively for 20months now, >> and I really like the program. However, when it comes to actually >> using the application itself, I still find that I obviously just >> don’t get it and that frustrates me. >> For example, with Firefox3 open, I pressed Insert-V and set Browse >> Mode to Do Not Auto-read. After making the change, I pressed >> Control-Backslash and saved the Set File. I thought this would make >> the change in Firefox alone. >> However I was wrong. Now Browse Mode behaves in this fashion any time >> it is active. >> Therefore, the question is how does one know what settings are global >> and what settings are specific to each set file, thus requiring the >> Set File to be saved? >> It has been 20 months with multiple reads of the Window-Eyes Manual, >> and the Window-Eyes program still confounds me on what I feel is a >> basic level. >> Within weeks, I knew what it took to make a setting global or >> specific to a particular configuration file using JAWS. >> >> Suzy, The Blind Avenger >> Doing my best to prove blind people can. >> >> >> >> >> >> If you reply to this message it will be delivered to the original >> sender only. If your reply would benefit others on the list and your >> message is related to GW Micro, then please consider sending your >> message to [email protected] so the entire list will receive it. >> >> All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, >> and can be searched through and sorted using the search form at the >> bottom of the page. >> >> If you wish to unsubscribe from this list, send a message to >> [EMAIL PROTECTED] and include leave gw-info in the body of the >> message. >> >> >> If you reply to this message it will be delivered to the >> originalÙ[™\ˆÛ›KˆYˆ[Ý\ˆ™\HÛÝ[™[™Yš]Ý\œÈÛˆH\Ý[™å½Õȵ•ÍÍ…”¥ÌÉ•±…Ñ• >> Ѽ\5¥É¼°Ñ¡•¸Á±•…Í”½¹Í¥‘•ÈÍ•¹‘¥¹œyour >> message to [email protected] so the entire list will receive >> it.[ÕËR[™›ÈY\ÜØYÙ\È\™H\˜Ú]™Y]‹ËÝÝÝË™ÝÛZXܛ˘ÛÛKÙÝÚ[™›Ë[™Ø[ˆ™HÙX\˜ÚY›ÝYÚ[™ÛÜY\Ú[™ÈHÙX\˜Ú›Ü›H]H›ÝÛHÙˆHYÙKˆb÷Rv—6‚FòVç7V'67&&Rg&öÒF†—2Æ—7BÂ6VæBÖW76vRFöÆ—7G6W'dwvÖ7&òæ6öÒæBæ6ÇVFRÆVfRwrÖæfòâF†R&öG’½˜Ñ¡”µ•ÍÍ…” >> > -- To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team. Aaron Smith GW Micro Phone: 260/489-3671 Fax: 260/489-2608 WWW: http://www.gwmicro.com FTP: ftp://ftp.gwmicro.com Technical Support & Web Development If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message. Protect Environment & Save Mother Earth *******************************Disclaimer******************************* The information contained in this message is BPCL's Confidential and Proprietary information and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, he/she is hereby notified that any use, dissemination, distribution, or copying of this communication or any of its content is strictly prohibited. In such case, please advise the sender immediately and delete it from your system. Further acknowledge that any views expressed in this message are those of the individual sender and no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of BPCL. *********************************************************************** If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message.
