Jamal, I'm hoping here that Mike will chime in here, since he's the maintainer. The only switch I know about is /A because it was used for keyboard layouts. However, that was with Window-Eyes pre 4.0 and even then I only saw its existence thanks to the keyboard layouts being present in the Window-Eyes program group instead of their current location somewhere on the Window-Eyes Keyboard menu.
There most be other switches though since it's used in the installer to dynamically apply the new default settings. Maybe it's closed with a wm_close, I really don't know. GW? On 08/07/2008, Jamal Mazrui <[EMAIL PROTECTED]> wrote: > Daren, > I just tried running Text2SET at the command line with an appropriate > input and output file, i.e., > > text2set.exe EdSharp.t00 EdSharp.000 > > It seemed to work except the GUI mode was entered, and the read-only > edit box remained on the screen. I would like the installer to do this > behind the scenes. , returning to the command line after the operation. > How can I do this? > > Jamal > On Tue, 8 Jul 2008 [EMAIL PROTECTED] wrote: > >> Date: Tue, 8 Jul 2008 20:17:28 +0100 >> From: [EMAIL PROTECTED] >> Reply-To: [email protected] >> To: [email protected] >> Subject: Re: Speech environment distributed with EdSharp >> >> Jamal, >> >> You're right, I did mean using Text2set to specify the associated Key >> Label Dictionary for the generated set file. >> >> This line should do it. >> >> Key_Label_Dictionary_File = edsharp.key >> >> By default, all set files are associated with keylab.key since this is >> what wineyes.000 is associated with. All you do is alter the >> association in your generated set file. Both keylab.key and your >> dictionary will be active whenever your dynamically generated Ed Sharp >> set file loads, since keylab.key is global. This is because all set >> files are derived from wineyes.000. >> >> Window-Eyes differs from jaws in that almost all settings are stored >> in a set file, and all dictionaries have meaning due to their >> associations with a set file. The only exception comes in with the set >> files themselves and their associations to applications, which as you >> know happen with the .we file. The .we file is now of even greater >> importance because of scripting. This has the effect of requiring set >> file format modifications to be made between Window-Eyes versions, >> since it is rare that a new file type for a new manager appears. >> However, the process of generating a set file with text2set has >> remained more or less constant throughout the history of Window-Eyes. >> Therefore, assuming the setting you want to include in your new set >> file existed back in Window-Eyes 1.0, there's no reason why that >> shouldn't be possible, other than the small factor of incompatible >> Windows versions and file locations *grin*. >> >> Daren >> >> On 08/07/2008, Jamal Mazrui <[EMAIL PROTECTED]> wrote: >> > Thanks, Daren -- I'll look into that technique. I'm not aware, however, >> > that TEXT2SET can specify a key label dictionary to be associated with >> > the set file being generated. Did you mean that, or specifying the >> > association in another way? >> > >> > Jamal >> > On Tue, 8 Jul 2008 [EMAIL PROTECTED] >> > wrote: >> > >> >> Date: Tue, 8 Jul 2008 19:20:20 +0100 >> >> From: [EMAIL PROTECTED] >> >> Reply-To: [email protected] >> >> To: [email protected] >> >> Subject: Re: Speech environment distributed with EdSharp >> >> >> >> Jamal, >> >> >> >> It's not possible to have a Key label dictionary file without a set >> >> file. However, it is possible to dynamically create a set file based >> >> on a user's wineyes.000 with the only modification of the Key Label >> >> dictionary association and the alternative file name i.e. edsharp.000. >> >> >> >> You could use a text2set command to do it. >> >> >> >> As for the automation approach, again I think thats possible. It seems >> >> you can do something like >> >> >> >> Const MyKeyFile = "edsharp.key" >> >> ActiveSettings.KeyLabelDictionary.Open MyKeyFile >> >> >> >> Text2set is probably your best bet since EdSharp won't be running when >> >> you perform this step. It also works regardless of the version of >> >> WIndow-Eyes being installed. >> >> >> >> I always forget the syntax of doing it on the command line, but all >> >> you'd need in the input text file is a line that looks like >> >> Key_Label_Dictionary = edsharp.key >> >> >> >> Best way to make sure is to decompile your wineyes.000 with Set2text, >> >> and search for a string similar to "Key_Label". >> >> >> >> Hope this helps. >> >> >> >> Darren >> >> >> >> On 08/07/2008, Jamal Mazrui <[EMAIL PROTECTED]> wrote: >> >> > yI did mean a .key rather than .lab file. Are you sure that one can >> >> > be >> >> > created programmatically via the object model (it seems like some set >> >> > file related features area read only in the object model)? To >> >> > clarify, >> >> > the EdSharp installer presents an optional Window-Eyes package to >> >> > install, the default option being unchecked. I do not want to make >> >> > assumptions about hotkey assignments and other aspects of someone's >> >> > set >> >> > files, so would prefer to just distribute a key label dictionary >> >> > without >> >> > a set file. Is this not possible? >> >> > >> >> > Jamal >> >> > On Tue, 8 Jul 2008 [EMAIL PROTECTED] wrote: >> >> > >> >> >> Date: Tue, 8 Jul 2008 18:48:26 +0100 >> >> >> From: [EMAIL PROTECTED] >> >> >> Reply-To: [email protected] >> >> >> To: [email protected] >> >> >> Subject: Re: Speech environment distributed with EdSharp >> >> >> >> >> >> Jamal, >> >> >> >> >> >> Key label dictionaries .key are associated with a set file. Since >> >> >> association by title isn't practical, class would indeed seem the >> >> >> way >> >> >> to go. >> >> >> >> >> >> Alternatively, you could just manually create the key labels >> >> >> yourself >> >> >> with the Window-Eyes.Application com instance, although that would >> >> >> of >> >> >> course only work for WE 7.0 or later, and probably require more >> >> >> effort >> >> >> on your part. The added benefits however to this latter approach are >> >> >> that other people won't have to download and install your customised >> >> >> speech environment, though that is of course also a huge >> >> >> disadvantage, >> >> >> as a speech environment dynamically created through the exposed >> >> >> Window-Eyes interface would probably be more difficult to >> >> >> permanently >> >> >> customise. Since many of us love Window-Eyes for its flexible >> >> >> verbosity, any decision along these lines deserves consideration. >> >> >> >> >> >> Anyway hope this helps. >> >> >> >> >> >> Darren >> >> >> >> >> >> On 08/07/2008, Jamal Mazrui <[EMAIL PROTECTED]> wrote: >> >> >> > I want to distribute a Window-Eyes speech environment with EdSharp >> >> >> > to >> >> >> > fine >> >> >> > tune speech in ways not practical otherwise. Initially, I just >> >> >> > want >> >> >> > a >> >> >> > custom set of key labels. Can I distribute a .lab file without a >> >> >> > .set >> >> >> > file? I looked at the content of a .we file after associating a >> >> >> > .lab >> >> >> > file, and did not find a reference to the .lab file, so is that >> >> >> > association stored in a .set file? Since EdSharp has a varying >> >> >> > title >> >> >> > depending on what MDI document is active, do I need to associate >> >> >> > with >> >> >> > the >> >> >> > window class rather than the title? I noticed that the >> >> >> > association I >> >> >> > created does not seem to work reliably, so wonder if this is the >> >> >> > cause. >> >> >> > >> >> >> > Jamal >> >> >> > >> >> >> > >> >> >> >> >> > >> >> >> > >> >
