Hi Ralf, I needed to do the same thing in Word; I have some speech which I felt needed to be spoken before the usual speech from WE (when arrow keys were used, just as in your case), and then i had other types of info which I felt should be spoken after WE spoke the contents of the line, etc. What i ended up doing was using the onCursorKey event to catch the arrow key being pressed. Using this event, you can find the exact moment where the application has acted on the arrow key (by moving the insertion point or whatever), but WE hasn't yet seen it. At this point (in the event handler when the before parameter becomes false), you can stop WE from seeing the key, and then queue your routine. your routine can speak it's part, and then eventually cause WE to do what it would have done by executing the action of the cursorKey object. At this point, you can additionally queue more speech, which will have the effect of being spoken after whatever WE has to say. so, it's a fair amount of work, but you can come close to having the control you want. I've just found one unexpected side effect: doing things this way inhibits the keyboard speech, so I've had to add that in myself. I don't see why preventing WE from acting on a cursor key keeps it from speaking the fact that you pressed the key, but it indeed seems to. There could be other unintended side effects, I don't know. If you'd like some code showing how I do this, drop me a line off list and I'll send it to you. Chip
_____ From: Ralf Kefferpuetz [mailto:[email protected]] Sent: Tuesday, June 21, 2011 11:29 AM To: [email protected] Subject: Controlling the order of speech output - Script/Application Hello all, maybe you can help me with some best practices in controlling the order of the speech output between an application and a running script. Let me explain: I have Excel running and when you move from cell to cell We says A1 CellContent, B1 CellContent, and so on. My script hooks on onChildRendered to get catch the movement of the cursor, then it gets the background color of the cell and speaks it. So far, so good, moving down (A1, A2, A3 and so on) works fine, WE speaks the background cell color and after this the cell address and the cell content. Moving horizontal (A1, B1, C1 and so on) does it the other way, means WE says the Cell address, the cell content and then the backgroundcolor, which comes from my script. Now my question, is there any way to control the order of the speech output, maybe with connecting to the speech onSpeak event? I tried it but it was not successful. Many thanks for your ideas, Ralf Ralf Kefferpuetz Germany From: RicksPlace [mailto:[email protected]] Sent: Tuesday, June 21, 2011 3:29 PM To: [email protected] Subject: Re: Setting WE Default Folder Path Hi Aaron: This would be before the user navigates to the ScriptPath. In other words when a scriptor wants to open a file but has not navigated into the Windoweyes Default Directory. Your method would work if I load the App into the Default Directory upon installation of the app which I will consider since that is how most scripts are loaded currently. That would take care of the question. Rick USA ----- Original Message ----- From: Aaron Smith <mailto:[email protected]> To: [email protected] Sent: Tuesday, June 21, 2011 8:07 AM Subject: Re: Setting WE Default Folder Path On 6/21/2011 6:03 AM, RicksPlace wrote: Hi: In my app I would like to set the WE Default Folder where the XML files are held as the initial directory for the standard MS OpenFile Dialog control. You can use ClientInformation.ScriptPath to get the directory where the script itself is located, or ClientInformation.UserProfilePath to get the current profile directory. Aaron -- Aaron Smith Web Development * App Development * Product Support Specialist GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com 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.
