Re: [orca-list] Solved (sorta) (was Re: I can not run eclipse with latest orca)

[jose vilmar estacio de souza <vilmar informal com br>]

Hi Joanie.
The bad news is that I will not get the eclipse and the current version 
of Orca until the team fix the bug and eclipse is part of my day job.
Even that fix quickly, which I believe will happen, will take a while 
until the new version is released for production.
Now I'm sad!
Thanks.
        
On 09/11/2010 06:47 AM, Joanmarie Diggs wrote:
> Hey José.
>
> As I have commented before, you are indeed the master of the 100%
> reliably reproducible test case.<smile>  Something I am eternally
> grateful for.
>
> So.... I have good news and bad news for you, as you may have already
> seen. The bad news is that I was right: I created a simple event
> listener script that listens for object:text-changed events and simply
> printed out information based on the event. Then I ran that script
> without running Orca. If I do not call event.source.getAttributes() the
> crash does not occur; if I do call event.source.getAttributes() and type
> slowly as you described, the crash occurs 100% of the time.
>
> The examination of AtkObject Attributes is actually a very, very basic
> thing for an AT to want to do. Thus the fact that this crasher has not
> come up until now is just dumb luck. As a result, I have filed the
> appropriate bug against Eclipse:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=325028
>
> That's all the bad news. The good news, of course, is that the Eclipse
> team is amongst the fastest, most responsive teams out there when it
> comes to addressing a11y bugs. So this issue will almost certainly be
> resolved by them soon.
>
> Thanks again for the report and your amazing test cases! Take care.
> --joanie