[Nvda-dev] problem interacting with audacity

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[Nvda-dev] problem interacting with audacity

Peter Vágner
Hello guys,
After a while I tryed to run Audacity today. It is know Audacity (or
better to say the toolkit they are using) has strange MSAA support but
we were able to do some workarounds. Until now it has been working
relativelly well. When some intensive processing was being performed by
audacity NVDA was locked and it was not able to provide access to
anything. Now it locks immediatelly after starting audacity. The problem
is not in the audacity appmodule because it also happens when that's
removed.
I just would like to ask if you have some ideas what might cause this
before I'll start examining older revisions trying to locate the change.

Peter


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] problem interacting with audacity

James Teh-2
Hi Peter,

I have no ideas as to exactly what might have caused this. However, you
might start looking around the time Mick rewrote the IAccessible event
handling stuff, which was r1864. I don't know exactly why this would
have caused problems for Audacity, but it was a pretty big set of
changes, so this seems a good place to start.

Jamie

Peter Vágner wrote:

> Hello guys,
> After a while I tryed to run Audacity today. It is know Audacity (or
> better to say the toolkit they are using) has strange MSAA support but
> we were able to do some workarounds. Until now it has been working
> relativelly well. When some intensive processing was being performed by
> audacity NVDA was locked and it was not able to provide access to
> anything. Now it locks immediatelly after starting audacity. The problem
> is not in the audacity appmodule because it also happens when that's
> removed.
> I just would like to ask if you have some ideas what might cause this
> before I'll start examining older revisions trying to locate the change.
>
> Peter
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev

--
James Teh
Email: [hidden email]
WWW: http://www.jantrid.net/
MSN Messenger: [hidden email]
Jabber: [hidden email]
Yahoo: jcs_teh


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] problem interacting with audacity

Peter Vágner
In reply to this post by Peter Vágner
Hello,

Peter Vágner  wrote:
> When some intensive processing was being performed by
> audacity NVDA was locked and it was not able to provide access to
> anything. Now it locks immediatelly after starting audacity. The problem
> is not in the audacity appmodule because it also happens when that's
> removed.

I have found the problems started in revision 1870. The change to
NVDAObjects\IAccessible\_init.py makes such a difference although I can
see nothing wrong with it. It looks very complicated so I may have
missed something. Could anyone please try looking into it?

Peter


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] problem interacting with audacity

Michael Curran
Hi,

Fixed in r1945.

Thanks Peter for tracking down the revision number... I would have never
found it. It ended up being some test code for testing gecko
node_child_of which I forgot to remove.

Mick



Peter Vágner wrote:

> Hello,
>
> Peter Vágner  wrote:
>> When some intensive processing was being performed by
>> audacity NVDA was locked and it was not able to provide access to
>> anything. Now it locks immediatelly after starting audacity. The problem
>> is not in the audacity appmodule because it also happens when that's
>> removed.
>
> I have found the problems started in revision 1870. The change to
> NVDAObjects\IAccessible\_init.py makes such a difference although I can
> see nothing wrong with it. It looks very complicated so I may have
> missed something. Could anyone please try looking into it?
>
> Peter
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev