Hmmm, I tried
dObj.Control("statusBar").Window.Type = wtStatus
But it doesn't seem to work.
dObj.Control("statusBar").Type = wtStatus
throws an error.
J.J> Meddaugh - ATGuys.com
Your Assistive Technology Experts
----- Original Message -----
From: Chip Orange
To: [email protected]
Sent: Tuesday, November 09, 2010 8:59 PM
Subject: RE: Hooking a WE Hotkey
Aaron,
after the dialog is up, couldn't he set the window type of his static window
to be that of a status bar, then wouldn't WE find it even if it weren't the
bottom most text?
Chip
------------------------------------------------------------------------------
From: Aaron Smith [mailto:[email protected]]
Sent: Tuesday, November 09, 2010 4:40 PM
To: [email protected]
Subject: Re: Hooking a WE Hotkey
On 11/9/2010 4:32 PM, J.J. Meddaugh wrote:
You can still use RegisterHotkey to do that.
Would I replace the hotkey with the HK enum in this case?
Doug reminded me that someone could change the hot key while your dialog is
up, so scratch that idea. On dialogcreate, hook OnHotkey. On dialogclosing,
unhook OnHotkey. Then, in your OnHotkey event handler, look to see if you get
an hkStatusLine. If so, do whatever you need to do, and return True. Otherwise,
return False.
Alternatively, is there a certain characteristic I can give to my statusbar
in the dialog box to make WE recognize it? I have it as a static item under the
listview currently.
The Window-Eyes status bar algorithm will use whatever the last line of text
is if it can't find a real status bar. So as long as your static is the last
thing in the dialog, the default status line reading behavior should work.
Aaron
--
Aaron Smith
Product Support Specialist * Web Development
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.
