Prev: ndp20-kb916002-x86.exe supperceded by .net 2 sp1?
Next: Dynamically creating an ActiveX on a WPF/Windows .Net app
From: Jozsef Bekes on 21 Aug 2008 13:09
> I would not personally use it to accomplish some other unrelated task.
Actually you're right... if I do not find a way that does not require me to
change the vb.net code I'll use your solution.

Thanks again!
Jozsi

"Peter Duniho" <NpOeStPeAdM(a)nnowslpianmk.com> wrote in message
news:op.uf8tp6bw8jd0ej(a)petes-computer.local...
> On Thu, 21 Aug 2008 06:27:52 -0700, Jozsef Bekes <bjdodo(a)hotmail.com>
> wrote:
>
>> Hi Peter,
>>
>> I have got a response in another forum. This looks better, although not
>> perfect:
>>
>> "You can fill "AccessibleName" property with unique ID string for a given
>> control. Then, from the tester application call
>> `AccessibleObjectFromWindow'
>> in order to obtain `IAccessible' interface for the control. Use the
>> `IAccessible::get_accName' method to identify your control."
>
> The IAccessible interface is part of the larger accessibility support in
> Windows. I would not personally use it to accomplish some other unrelated
> task. YMMV.
>
> I also don't see how using that is significantly better than setting the
> GWL_ID value explicitly in code. The only significant difference between
> the two is in how the ID information is entered. Maybe it's marginally
> easier to enter that ID in the VS Designer, but it's not that hard to just
> write the code to assign it either.
>
> Pete


First  |  Prev  | 
Pages: 1 2
Prev: ndp20-kb916002-x86.exe supperceded by .net 2 sp1?
Next: Dynamically creating an ActiveX on a WPF/Windows .Net app