Hi Guys: This can be handled by having the root set file and not allowing a user to modify it directly. A user could override or extend it in another file but the root content always remains the same. When an update comes in it replaces the root file but if the design is good anything in the user file will remain intact. This is accomplished via what Microsoft calls partial classes for working in some DataBase projects using strongly typed data sets. To change a setting in the root file you would override that setting in your partial file and when WindowEyes engine fires up it loads both into one file that it uses during the runtime environment. The only requirements are that any changes to the root file like brand new settings or deprecated settings are handled in the users file but that is still allot easier than ReCreating the file by modifying the AI2 version from scratch and if you don't like your user file rename or delete it and the factory settings in the AI2 version are loaded and used as usual. You could even have several versions of your user files each handling a single feature if you wanted to go that route or one for particular operating systems or hardware configurations. This may be able to be done now, don't know since I havent looked into it, but it could be done for sure if AI2 implemented it. Perhaps it could even be scripted. If the root set file variables and names don't change often this would be a way to maintain the custom user settings without limiting set file updates. The other option would be to allow the user to pick which set files to use and when a root file is updated that file might change but the user file would be intact and the one used at runtime, perhaps that is how it now works. But this is a good question and one that has been addressed for many years as distributed programs and data bases have been the norm to avoid stepping on allowed user changes to configuration or settings files.There may be others but I am aware of and used both of the above in other projects and platforms. Rick USA
-----Original Message----- From: Talk [mailto:talk-bounces+ofbgmail=mi.rr....@lists.window-eyes.com] On Behalf Of Chip Orange via Talk Sent: Sunday, August 2, 2015 4:37 PM To: 'Peter Duran' <peterduran2...@outlook.com>; 'Window-Eyes Discussion List' <talk@lists.window-eyes.com> Subject: RE: WE 9.2 and Factory Settings Thanks Peter for passing on this tip to all of us. I think that's a good suggestion (to automatically at least notify you that a .set file is out of date, if not allow you to have it automatically updated). The reason it isn't just "done" is that someone might have spent a lot of time modifying the settings (say for Word), so that very specific items are read, and others aren't. Maybe they defined a lot of hotkeys as having a "program" scope, then changed them to be something else so they don't conflict with something in Word. If so, all of this is lost when the later .set file is updated (replaced) on top of the out of date one; not to mention the issue of defined graphics, colors, exceptions, etc. They all could be lost, and people might not be happy. So, perhaps just notifying you is the best that can be done. Chip -----Original Message----- From: Talk [mailto:talk-bounces+chip.orange=gmail....@lists.window-eyes.com] On Behalf Of Peter Duran via Talk Sent: Saturday, August 01, 2015 4:44 PM To: Talk Subject: WE 9.2 and Factory Settings Hello I reported that, after the installation of WE 9.2, Word 2010 began to act crazily. For instance, paragraph styles were spoken at odd times, before reading a paragraph (as usual) or after reading a paragraph, or not at all. It took me several days to track down the cause of this anomaly. Finally, I went, for lack of other options, to the Factory Settings list under the File menu of Window-Eyes. I was told that the factory settings for Word 2010, Window-Eyes Global UI, and so on, were out of date. I install the latest factory settings for those programs I frequently use. My problems with Word 2010 went away, and Word 2010 behaved as before and even better in many ways. Question: Why didn't the WE Installer install the latest factory settings automatically? Peter Duran _______________________________________________ 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/talk-window-eyes.com/chip.orange%40 gmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ 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/talk-window-eyes.com/ofbgmail%40mi. rr.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ 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/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
