Hello.
I do not know if this is an issue with window-eyes or if it's a Writer issue. When I load Writer
with Window-eyes 8.4, I receive the following error.
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files\LibreOffice 4\program\soffice.bin
R6025
- pure virtual function call
If I load writer subsequent times using window-eyes, this error does not appear. Instead, it just
says that LibreOffice has stopped working and I eventually am focused on a close button. This
error only happens with Window-eyes. I've reported it to GW Micro, just in case it's something
they can correct.
David Goldfield
Computer Technology Instructor
919 Walnut Street
4th Floor
Philadelphia, PA 19107
215-627-0600 ext 3277
FAX: 215-922-0692
dgoldfie@asb.org<mailto:dgoldfie@asb.org>
www.asb.org<http://www.asb.org>
Give a Donation
http://asb.org/index.php?option=com_jdonation
Serving Philadelphia's and the nation's blind and visually impaired population since 1874.
--
To unsubscribe e-mail to: accessibility+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-accessibility] Window-eyes 8.4 and Writer 4.2 RC2 · David Goldfield
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.