Doug,
I just launched word as the document area is a custom control. I put
the mouse over the document window and brought up immed and typed:
print typename(mouse.window.control)
and I got "Control" as the result. Just to verify I then did:
print mouse.window.type
and got 11 which is cust
Jon says he's seeing this issue on controls that WE calls custom
controls.
On Thu, Dec 09, 2010 at 10:14:08AM -0500, Ron Parker wrote:
I just looked at the code, and the only reason you should ever fail to
get a Control object for a window would be if the window itself isn't in
the Window-Eyes
I just looked at the code, and the only reason you should ever fail to
get a Control object for a window would be if the window itself isn't in
the Window-Eyes OSM for some reason. That should be fairly rare.
On 12/9/2010 10:04 AM, Doug Lee wrote:
Yes this is very helpful info. The only rem
Doug,
Are you saying not all Window object can derive a Control object? I've
not see that if that is the case. But I have seen that the Next and
Previous properties of a Control don't always return an object. Usually
that means it is an overlap window or something. but if you are talking
Yes this is very helpful info. The only remaining concern I can see
is that my coworker, Jon, reports that not all windows have .control
objects associated with them.
On Thu, Dec 09, 2010 at 09:49:34AM -0500, Doug Geoffray wrote:
Then yes, the Window.Control.Previous and Window.Control.Next will
Then yes, the Window.Control.Previous and Window.Control.Next will get
you the previous and next window in Z order (also commonly referred to
as tab order). In fact when you use these properties, Window-Eyes
simply calls the GetWindow function with either GW_HWNDPREV or GW_HWNDNEXT.
You may a
I don't know my coworker's exact use case, but one I can think of is
when a control in focus is predictably labeled by the control prior to
it in Z order, or the prior Static control in Z order, or less
commonly, by the prior Static to the focused control's parent or
grandparent. Screen readers so
Hello Doug L,
Regarding your Z order question... Can you give me a specific example
what you are needing this for? Maybe that would help us give you a
better idea of what you can currently do or something we could add in
the future.
Thanks,
Doug G
On 11/22/2010 3:33 PM, Doug Lee wrote:
W
from what i heard, all this will be fixed or accessible by window-eyes 8 wich
is still not out even though gw has mentioned it a lot this year.
On Dec 9, 2010, at 6:52 AM, RicksPlace wrote:
> Hi: Any word on when WE may suppport the new accessibility hooks used by
> Microsoft so we can use Vis
Rick,
We have good news for you but I'm not ready to spill all the beans just
yet. We'll be talking a lot about this shortly.
Regards,
Doug
On 12/9/2010 6:52 AM, RicksPlace wrote:
Hi: Any word on when WE may suppport the new accessibility hooks used
by Microsoft so we can use Visual Studio
Hi: Any word on when WE may suppport the new accessibility hooks used by
Microsoft so we can use Visual Studio 2010 and subsequent versions of new MS
Software like Silverlight? Everything is heading into Windows Presentation
Foundation coding and away from the older Standard UI components for
d
11 matches
Mail list logo
