wxAccessible and accessing objects after deletion

[Leland]

I'm having a problem with wxAccessible and am looking for advice on how 
best to handle it.

What's happening is that accessibility aids (Jaws in this case) can 
attempt to use an accessible object after it's been deleted.

If my research on this is correct, the problem is merely a timing 
issue...Jaws gets the object to gather information, but the windows get 
destroyed before Jaws has an opportunity to access the info.

It can happen quite readily when displaying a wxProgressDialog.  Jaws 
sometimes attempts to query the gauge after the dialog goes away.

One solution for this appears to be to retain a backlog of deleted 
accessible objects and have them return failure if accessed after they 
are deleted.

But, I wanted to see if anyone else was using wxAccessible and 
experiencing the same issue.

Thanks,

Leland