Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
JAWS for Windows and VFP
Message
De
15/08/2002 01:12:03
 
 
À
14/08/2002 22:57:02
Gil Munk
The Scarborough Group, Inc.
Baltimore, Maryland, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00689839
Message ID:
00689853
Vues:
14
>Hi,
>
>JAWS from Freedom Scientific is screen reading software. If anyone has worked with this successfully in conjunction with Visual FoxPro 5.0 I'd be happy to get some pointers. I have JAWS 4.02.52 (Their latest version) and every control (textbox, splash screen text, title bar text, etc...) gets assigned a Control ID of 0 and a Class of #32769. The application that a potential client wants this to work with uses all VFP Base class controls. Short of replacing every control with a subclassed control of the same type I'd like to know if it's possible to change either the control ID and/or the Class that JAWS sees.

This is a SWAG, but VFP controls are not "real" Windows controls - I believe they don't have a window handle (hWnd). If this is what JAWS expects to work with you may be out of luck, subclassed VFP controls or not. The ID of 0 and Class of 32769 (32K + 1) looks suspiciously like some sort of default return value when it can't get any real information at all.

One option would be to replace all your controls with ActiveX controls which I believe have real hWnds.

Another might be to upgrade to VFP7. IIRC it still does not offer true "Windows" controls but it is specifically designed to be compatible with Active Accessibility so it may fit in with what you're trying to do. From the VFP7 docs:

*******
In the past, Visual FoxPro supported multiple platforms including DOS, Macintosh and Unix. Because of its cross-platform nature, a number of user interface elements, including form controls, are drawn natively by Visual FoxPro rather than using common Windows UI classes. Accessibility aids and test tools that rely solely on applications using common Windows UI classes do not function fully with Visual FoxPro.

Recently Microsoft has published a new accessibility standard known as Microsoft Active Accessibility, which centers on applications and accessibility clients communicating through a common set of interfaces. Accessibility aids and test tools written in compliance with these new accessibility interfaces can now work directly with applications that implement these interfaces.

Visual FoxPro supports Microsoft Active Accessibility 2.0 and implements full support for all Visual FoxPro user interface elements such as forms, dialog boxes, and menus, at design time and at run time through the accessibility interfaces (IAccessible).

The Accessibility Browser can be used to verify the accessibility features of your application using the IAccessible properties of objects. It can also be used to help you create automated test suites.

The Automated Test Harness tool has been built on Microsoft Active Accessibility (MSAA) technology and can be used with all Visual FoxPro applications to test for accessibility issues. The Mouse and Keyboard events in the Visual FoxPro applications can be recorded and played back at any time.
*******
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform