As I've said we think we know what is causing the loss of speech at
least when it relates to browse mode. We haven't duplicated any
other losses of speech internally now that our new code to get
information during a lockup has been implemented. We are working to
fully understand this and will resolve it as soon as we can. We'll
just have to agree to disagree on your other points. The other
problems in browse mode are not catestrophic show stoppers. They
mostly relate to previous position not working which is anoying, but
not terrible. From our tech support we just don't get that many
complaints about it so we have to work on what is being most
requested even if that work isn't scratching your particular
itch. Bottom line we will make browse mode a top priority for the
next major release, but it won't be a service pack or a bug fix
because it is a large project that will take considerable resources
so once the next major release comes out you and I will no longer be
discussing this.
At 12:17 PM 10/14/2008, you wrote:
Speculation is such an interesting thing.
I have not speculated on any thing.
I also have not said you guys are stopping the use of msaa.
I have said:
I thought this was the ms solution that would work much better than
other options because gw was working directly with ms on this.
This never materialized.
The facts are it has never worked correctly.
didn't consider the need for multiple simultaneous buffers.
We have needed that since it came out and I personally called gw
tech support and focused directly on that huge need.
I agree with the rewrite and also agree that new technologies have changed
My main point is that I personally think this is of such great
importance that we need to put it at the top of the list in my opinion.
I think it effects so many of the applications that we need so bad
to stay employed.
I think the loss of speach issues followed by the browse mode issues
are the two greatest needs we have.
Any one else want to add wait to this view?
My goal here is not to fight about who said what or who is right.
I am just trying to focus on the tremendous need to resolve these issues.
For some reason even though browse mode has never worked correctly
we keep adding more features word, xl, power point, itunes and
scripting to name a few.
we are not just going to just knee jerk react and rush out something
to silence people on this list. We are going to rework our browse
mode code base and do it correctly which is a much better long term strategy.
I think that's a great plan!
However, I don't think you can call the delay in resolving these
issues as a knee jerk reaction ... these have been issues for years.
These are not new problems.
Yes they are incresed in 7.0 but, they are the same.
Now it's not about trying to tell you how to do your job it's about
timing on this issue.
I am praying we work on this asap as a huge bug fix not a group of
new features.
I am also praying we get this need resolution before several more
new features that push this issue to the back seat again.
Thanks for listening.
Sam
----- Original Message -----
From: <mailto:[EMAIL PROTECTED]>Michael D. Lawler
To: <mailto:[email protected]>[email protected]
Sent: Tuesday, October 14, 2008 9:17 AM
Subject: Re: WE 7 and browse mode
Speculation is such an interesting thing. We never said we were
going to stop using MSAA. We are doing a rewrite because browse
mode is over 10 years old and when it was created we didn't consider
the need for multiple simultaneous buffers. The issues with AJAX
and ARIA didn't exist. WE scripting which requires a lot more from
browse mode didn't exist. Browse mode was created when we supported
9X which made it more complex code wise than it needed to be. From
our perspective there is only one browse mode related problem that
is a show stopper and that is a lockup where WE hangs under certain
timing conditions when browse mode has been told to turn off and
then immediately turn back on. We, with the new lockup code that I
said we would work on post 7.0, are currently working to understand
this issue enough to hopefully resolve it. The other issues,
honestly, are anoyances that don't prevent people from functioning
with browse mode and we are not just going to just knee jerk react
and rush out something to silence people on this list. We are going
to rework our browse mode code base and do it correctly which is a
much better long term strategy.
At 11:02 AM 10/14/2008, you wrote:
I understand the below:
The only problem I have it back when browse mode was developed we
were told that msaa was great.
Other screen reader companies did there own proprietary stuff for
this and gw was working with microsoft with msaa to do it right.
Browse mode took a while etc.
It's never worked correctly ... why the complete rewrite?
When will this be done?
I think most of us use the applications taht use browse mode the
most of all apps.
We need to truly get this fixed as soon as we can and certainly
beofre we start adding more features.
Thanks so listening to my views.
Sam Bushman
----- Original Message -----
From: <mailto:[EMAIL PROTECTED]>Michael D. Lawler
To: <mailto:[email protected]>[email protected]
Sent: Tuesday, October 14, 2008 8:55 AM
Subject: Re: WE 7 and browse mode
We only stated that browse mode was going to be redone post
7.0. This is a major project and won't be released in any service
pack or minor update.
At 09:11 AM 10/14/2008, you wrote:
Did I understand it correctly from the GW staff that they would be
coming out with a WE 7 service pack soon after the release of WE 7
which would fix the browse mode problems that seemed to get worse
with the new release?
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list
and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive
it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through and
sorted
using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
Michael D. Lawler
Voice 260-489-3671
Fax 260-489-2608
Internet mailto:[EMAIL PROTECTED]
web http://www.gwmicro.com
ftp ftp://ftp.gwmicro.com
GW Micro, Inc.,
Development Liaison and Technical Support Supervisor
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list
and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive
it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through and sorted
using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through and sorted
using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
Michael D. Lawler
Voice 260-489-3671
Fax 260-489-2608
Internet mailto:[EMAIL PROTECTED]
web http://www.gwmicro.com
ftp ftp://ftp.gwmicro.com
GW Micro, Inc.,
Development Liaison and Technical Support Supervisor
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
and can be searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
--
Michael D. Lawler
Voice 260-489-3671
Fax 260-489-2608
Internet mailto:[EMAIL PROTECTED]
web http://www.gwmicro.com
ftp ftp://ftp.gwmicro.com
GW Micro, Inc.,
Development Liaison and Technical Support Supervisor
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
