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 > > > > >
