On 22.12.2009 00:23, Serge Tumanyan wrote:
>> But I've changed the accRole property to "link" for those controls and I
>> thought that this would be enough for the screen readers to recognize
>> them as such?
> I hoped so to. But they are announced as text by mighty screenreaders as
> JAWS for example, though Thunder that is not very powerfull and takes only
> MSAA information into account works properly.
Well, they *are* text labels but clickable - a lot of custom controls
are based on the label control so I'm not sure why JAWS can't figure
this out properly.
> I am not very familiar with MFC that is used to develop TSVN, but at least
> using WUI you can for example get the information of a class by calling
> 'GetClassInfoEx', then change the class name by changing the 'lpszClassName'
> member of the 'WNDCLASSEX' structure leaving the other fields untouched to
> preserve the functionality of the newly registered class and 'lpfnWndProc'
> callback procedure to be taken from original class and then register class
> by calling 'RegisterClassEx' function - this will not change the
> functionality of the newly registered class from the original one. Isn't
> something similar possible in MFC?
Well, that's certainly possible. But that's not really renaming the
class but creating a completely new window class and borrowing most of
the original data from the original window class.
This only works if the original windowproc function never uses the class
name for e.g. checks about what to do. And since that's not really
documented, I don't want to do that - it could change without notice and
break our link controls completely.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-22 22:15:02 CET