Re: [g-a-devel]not using oneway ...
- From: Bill Haneman <bill haneman sun com>
- To: Michael Meeks <michael ximian com>
- Cc: accessibility mailing list <gnome-accessibility-devel gnome org>
- Subject: Re: [g-a-devel]not using oneway ...
- Date: 17 Jun 2002 08:57:53 +0100
On Mon, 2002-06-17 at 08:37, Michael Meeks wrote:
> Hi Bill,
>
> One issue with not using oneway - which is the flip side to the
> problem, is that we are going to need methods to block re-enterancy
> during outgoing a11y calls. Gtk+ code [ and ~all client code ] is not
> designed to handle arbitrary re-enterancy through signal emission - or
> whatever hooks a11y is using.
>
> So - Gtk+ apps will need some method to call
> 'ORBit_push/pop_no_reenter' to use around the notifyEvent call,
> otherwise we just added a highly uncontrolled incoming re-enterancy
> point...
Why is this a new issue with 'no oneway' ? It's already the case with
key event notification.
It's not clear to me that we can do this. I am a little alarmed to hear
this being raised at this late date.
-Bill
> Hmm;
>
> Michael.
>
> --
> mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]