Hi Doug, this agrees pretty much with my ideas. Steve Clower also just said they include reclassed control info, and field labels as well, and so he sometimes includes them in his .wepm packages when he has modified these pieces of info, and needs this to go to the user along with his app. I don't know if the .wepm installer would merge any included .we with any existing one, or just overwrite it.
one thing I do know unfortunately is that if you have installed program-specific apps, and so they have modified your .we file for the program, and then you reinstall the factory default set file for this program, it will overwrite your .we with the factory default one, and you will lose all of your associations without warning; your apps will simply fail to run the next time you run the program. I imagine you'd also lose any reclassed control info, and field labels as well. Looks like a topic for a nice GW support kb article or wiki article <grin> Chip -----Original Message----- From: Doug Lee [mailto:[email protected]] Sent: Saturday, April 23, 2011 6:55 PM To: [email protected] Subject: Re: Where Does .we file get created? Pardon if I missed any important content of this thread... Here is what I know, or think I know based on impirical evidence, about .we files: They are what connects set files and scripts to applications. They are always named after the application to which they apply. I believe the name of a .we file for an application must be the same as that application's file name, but with a .we extension instead of a .exe extension. I don't know if a .we file is ever named after a .dll file though. A .we file can contain references to scripts and set files, perhaps more. When an application loads, all refefiles referenced in the application's .we file are also loaded. In the case of scripts, they are run. When an application closes, the files referenced by its .we file are also unloaded. Notice that this loading and unloading is tied to when the application is running, not to when it is in focus. .we files are updated when you add a set file or a script file association to an application. They are also updated and/or created when you run a .wepm file, because that also creates associations for scripts and/or set files. I don't know of any occasion when one should include a .we file in a .wepm file, nor do I know what would happen if you do, since the .wepm file's running will itself alter any .we file for which it updates application associations. All, feel free to update and/or correct me here. This is what I believe to be true about these files. On Sat, Apr 23, 2011 at 06:41:20PM -0400, Chip Orange wrote: yes, you're quite right, they are stored in the window-eyes profile dir. I thought Rick's question was more along the lines of how are they created, and what information is stored in them, etc. Chip -----Original Message----- From: net bat [mailto:[email protected]] Sent: Saturday, April 23, 2011 6:28 PM To: [email protected] Subject: Re: Where Does .we file get created? they are saved in the users acount in appdata\roaming\gwmicro\window eyes\users\default folder. ----- Original Message ----- From: "Chip Orange" <[email protected]> To: <[email protected]> Sent: Saturday, April 23, 2011 3:18 PM Subject: RE: Where Does .we file get created? > Sorry to say Rick, but there appears to be no documentation that I > could find anyway, in the WE manual on whatever .we files are. > > Chip > > > > _____ > > From: RicksPlace [mailto:[email protected]] > Sent: Friday, April 22, 2011 9:36 AM > To: [email protected] > Subject: Where Does .we file get created? > > > Hi Guys: My app is NotePad2011.vbs and xml. I understand I should find > NotePad.we to associate with the vbs file. This is not working. Where > do the .we files come from and could the .we file be bad? > Thanks: > Rick USA > > > > __________ Information from ESET Smart Security, version of virus > signature database 6066 (20110423) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
