App Development

WEEvent 4.5.5

  by Ai Squared This app is rated 5 out of 5 stars with 2 ratings. XML Feed for WEEvent 4.5.5

WEEvent allows you to select many of the Window-Eyes scripting events and monitor their results in real time and or by logging the information to a specified file.

Control-Shift-Windows-E displays the main dialog allowing you to select the information you wish to monitor. The different events are put into the corresponding objects with matching checkboxes. For example all Application events are grouped in the Application checkbox and so on. You need to check the appropriate group of the events you wish to monitor. There is a Check All or Check None button which will either check all the event groups or uncheck all the event groups. Once you have the groups you need selected then the corresponding events from those groups will be displayed in the Available Events multi-selection listbox. Arrow to the specific event you wish to monitor and hit the space bar to select it or if it is already selected the space bar will unselect the event. Do this for all events you wish to monitor. There is a Select All and Select None button that will either select all the events in the listbox or unselect all the events in the listbox.

Once you have the events you wish selected the logging will start once activation leaves the WEEvent dialog. So for example, alt-tab to the application you wish to monitor the events for. By default the events will be logged to the Event History edit box located in the WEEvent dialog. Simply alt-tab back to WEEvent or press the default hotkey once again. You can tab to the Event History edit box to review the events which were logged. Note while WEEvent is active, no logging will occur.

If you tab off of the Event History edit box you will be placed on either the Disable Logging or Enable Logging button. This can be used to disable logging even though events are selected and activation is off of the WEEvent dialog. A more useful way to toggle the logging on and off is to use the second hotkey, Control-Windows-E. This works just like the button but can be used even when activation is away from the WEEvent dialog. This allows you to get to the exact point you want to start logging without seeing all the intermediate events. Once you are where you wish to start logging, press the Toggle Logging hotkey to turn it on and when you are done, you can turn off logging to prevent other frivolous events from being logged as you get back into the WEEvent dialog to review the events.

Past the Disable/Enable logging button, there is a Clear History button which will clear the contents of the Event History edit box. Following this is a Help button allowing you to check for updates and change the default hotkeys. Finally there is a Close button which acts the same as hitting the escape key while in the dialog. Logging will stop if you close the WEEvent dialog.

If you are using Window-Eyes 7.1 or newer you’ll notice there are two menu options. The File menu gives you a Save As option which will prompt you for a filename and then will save the contents of the Event History edit box into that file. The other File menu option is Close which acts the same as the Close button on the main dialog or hitting escape in the dialog.

The other menu option is called Options. This offers five options.

Logging Options brings up a dialog allowing you to set your logging options. Log To Event History Window will cause the logging information to go to the Event History edit box. Log To Debug Window will cause the logging information to be sent to any debugger window you have on your system such as WinDbg or DbgView. Log to File allows you to select a file to have the logging information sent to. You can also specify if you want the information to overwrite the existing file or append to the end. The Add Timestamps checkbox will cause a timestamp to be placed at the beginning of each log entry. Log Active Window Process Events Only (Window / MSAA) check box will cause the logging for MSAA and Windows events to only be logged if they are for the currently active window. Meaning if this were checked and an event fires for a window that is not associated to the active window, it will be ignored.

The next menu option off of the Options pull down allows you to select specific information you want logged for MSAA and Window events. The MSAA Information To display option brings up a dialog with several checkboxes allowing you to select which items from the MSAA event to include in the log. Window Information To Display brings up a similar dialog with several checkboxes allowing you to select which items from the Window event to include in the log.

The Remember Size and Position off of the Options menu will cause the WEEvent window to remember its current position and size and next time it is brought up will force it to the same size and position each time.

The Always On Top menu option will force the WEEvent dialog to always be the top most window even when it isn’t the active window.

Download Now

Supported Languages: English

Minimum Version: Window-Eyes 7.0

Version 4.5.5

2/3/2016 11:50:46 AM
  • Added support for the Speech.OnStateChange event.

Read more about WEEvent


File Details:

  • Filename: weevent.wepm
  • Date: 2/3/2016 11:50:48 AM
  • Size: 36.2KB
  • Total Downloads: 12770

DISCLAIMER: Ai Squared DOES NOT ASSUME AND IS NOT RESPONSIBLE FOR ANY LIABILITY WHATSOEVER FOR THE CONTENT OF THIS, OR ANY EXTERNAL, APP, THE OPERATION OR CONTENT (INCLUDING THE RIGHT TO DISPLAY SUCH INFORMATION) OF ANY APP, NOR FOR ANY OF THE INFORMATION, INTERPRETATION, COMMENTS OR OPINIONS EXPRESSED IN ANY APP. ANY COMMENTS OR INQUIRIES REGARDING THIS APP ARE TO BE DIRECTED TO THE PARTICULAR PERSON OR PERSONS RESPONSIBLE FOR AUTHORING AND PROVIDING THE APP.


Comments

On 7/20/2011, JaredW wrote:

A must have tool for any developer.

On 6/15/2011, corange wrote:

This is something every single app developer should have; whether beginner or old-timer, WE Event is absolutely a necessity for determining how to approach improving the accessibility of any program.

On 3/29/2008, sclower wrote:

This script provides an easy but powerful way to monitor a program's events. I recommend anyone use this when scripting a new application.