2. = another app is=20 active and has the focus; it is a Terminal app (user@ubuntu8041...)

The=20 experiment sets up the above situation then clicks just = once on the=20 pushbutton in the GUI app. That single click causes a sequence of=20 events to unfold that terminates with the dialog as the active=20 window.

I = first ran this=20 experiment while executing an at-spi logging app that I've = written. =20 When I clicked on the pushbutton, these events and only these = events were logged:

TCF 40:34.041: ev = window:activate (det1: 0x0, det2: 0x0) Hello World plus(frame)
TCF = 40:34.060:=20 ev window:deactivate (det1: 0x0, det2: 0x0) user@ubuntu8041:=20 ~/ldtp-1.3.0/src(frame)
TCF 40:34.061: ev window:create (det1: 0x0, = det2:=20 0x0) Information(alert)
TCF 40:34.188: ev window:deactivate (det1: = 0x0, det2:=20 0x0) Hello World plus(frame)
TCF 40:34.189: ev window:activate (det1: = 0x0,=20 det2: 0x0) Information(alert)
TCF 40:34.202: ev focus: (det1: 0x0, = det2: 0x0)=20 No(push button.=3Dnothing=3D) Mouse (934, 602) not in Focus = <(x:1002..1086,=20 y:616..651) (w:85, h:36)>

No mouse events = were=20 reported. I was expecting = mouse:button:1p and=20 mouse:button:1r, but they never showed = up. I=20 reran the experiment a few times and got the same=20 result.

I decided to run = Accerciser=20 while running this experiment. I set it up to monitor the = same events=20 for which my logging app is listening. Wither Accerciser = running, every time I ran the experiment the expected mouse events = appear,=20 both in my logging app and in accerciser. This caused me to = suspect that=20 accerciser is setting something up that my logging app is=20 not.

So next = I stopped my=20 logging app and just run the experiment with = Accerciser monitoring=20 events. When Accerciser is the only app listening for at-spi = events,=20 it gets the same result as I originally observed: no mouse = events are=20 reported.

Now that I've = written all this,=20 it seems to me like this could be a bug in at-spi -- I clicked on the=20 pushbutton, the associated events should be delivered to all listeners = shouldn't=20 they? The pushbutton is clearly getting the "clicked" signal, = because it=20 is that signal handler that brings up the alert=20 dialog.

-Sam

Here's the = Accerciser log=20 showing that it doesn't get any mouse events=20 either:

focus:(0, 0,=20 None)   -- clicked on the Terminal = app=20 to make it active and set up the = experiment
   =20 source: [terminal | Terminal]
    application: = [application |=20 gnome-terminal]
window:activate(0, 0, Hello World plus)   = -- click on pushbutton
    = source: [frame=20 | Hello World plus]
    application: [application |=20 gtk_hello]
window:deactivate(0, 0, user@ubuntu8041:=20 ~/ldtp-1.3.0/src)
    source: [frame | user@ubuntu8041:=20 ~/ldtp-1.3.0/src]
    application: [application |=20 gnome-terminal]
window:create(0, 0, = Information)
   =20 source: [alert | Information]
    application: = [application |=20 gtk_hello]
window:deactivate(0, 0, Hello World = plus)
   =20 source: [frame | Hello World plus]
    application:=20 [application | gtk_hello]
window:activate(0, 0,=20 Information)
    source: [alert |=20 Information]
    application: [application |=20 gtk_hello]
focus:(0, 0, None)
    source: [push = button |=20 No]
    application: [application |=20 gtk_hello]

Here is my app's = log when the=20 mouse events are delivered (the MOUSE events are device=20 events):

TCF 34:03.390: ev = mouse:button:1p (x: 1081, y: 610) = main(unknown)
TCF=20 34:03.385: ev MOUSE key: 1(), keycode: 1, type: button-pressed, = modifiers 0x100=20 xxx:1081 yyy:610 []
TCF 34:03.392: ev window:deactivate (det1: 0x0, = det2:=20 0x0) user@ubuntu8041:=20 ~/ldtp-1.3.0/src(frame)
TCF 34:03.443: ev window:activate (det1: 0x0, = det2:=20 0x0) Hello World plus(frame)
TCF 34:03.531: ev MOUSE key: 1(), = keycode: 1,=20 type: button-released, modifiers 0x0 xxx:1081 yyy:610 []
TCF = 34:03.539: ev=20 mouse:button:1r (x: 1081, y: 610)=20 main(unknown)
TCF 34:03.615: ev window:create (det1: 0x0, det2: 0x0)=20 Information(alert)
TCF 34:03.635: ev window:deactivate (det1: 0x0, = det2: 0x0)=20 Hello World plus(frame)
TCF 34:03.638: ev window:activate (det1: 0x0, = det2:=20 0x0) Information(alert)
TCF 34:03.660: ev focus: (det1: 0x0, det2: = 0x0)=20 No(push button.=3Dnothing=3D) Mouse (1081, 610) not in Focus = <(x:1186..1270,=20 y:626..661) (w:85, h:36)>

Here is = Accerciser's log when=20 the mouse events are delivered.

window:deactivate(0, 0, user@ubuntu8041:=20 ~/ldtp-1.3.0/src)
    source: [frame | user@ubuntu8041:=20 ~/ldtp-1.3.0/src]
    application: [application |=20 gnome-terminal]
mouse:button:1p(1081, = 610,=20 None)
    source: [unknown | = main]
   =20 application: None
window:activate(0, 0, Hello World=20 plus)
    source: [frame | Hello World=20 plus]
    application: [application | = gtk_hello]
mouse:button:1r(1081, 610, = None)
   =20 source: [unknown | main]
    application:=20 None
window:create(0, 0, Information)
    source: = [alert |=20 Information]
    application: [application |=20 gtk_hello]
window:deactivate(0, 0, Hello World = plus)
   =20 source: [frame | Hello World plus]
    application:=20 [application | gtk_hello]
window:activate(0, 0,=20 Information)
    source: [alert |=20 Information]
    application: [application |=20 gtk_hello]
focus:(0, 0, None)
    source: [push = button |=20 No]
    application: [application |=20 gtk_hello]

------_=_NextPart_001_01C95E4D.A7F27F98-- From Li.Yuan@Sun.COM Mon Dec 15 02:37:34 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 213CC75009D for ; Mon, 15 Dec 2008 02:37:34 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.373 X-Spam-Level: X-Spam-Status: No, score=-5.373 tagged_above=-999 required=2 tests=[AWL=2.226, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FwK5dxA4a+Ld for ; Mon, 15 Dec 2008 02:37:23 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id 9861175006A for ; Mon, 15 Dec 2008 02:37:15 +0000 (GMT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBF2bApL018802 for ; Mon, 15 Dec 2008 02:37:13 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KBW00H01CGD1G00@mail-apac.sun.com> (original mail from Li.Yuan@Sun.COM) for gnome-accessibility-devel@gnome.org; Mon, 15 Dec 2008 10:37:10 +0800 (SGT) Received: from [129.158.217.197] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KBW005QXCLXM5B1@mail-apac.sun.com>; Mon, 15 Dec 2008 10:37:10 +0800 (SGT) Date: Mon, 15 Dec 2008 10:36:39 +0800 From: Li Yuan In-reply-to: Sender: Li.Yuan@Sun.COM To: "Quiring, Sam" Message-id: <4945C2B7.5090401@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 2.0.0.18 (X11/20081125) Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] Interesting event reporting X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 02:37:34 -0000 Quiring, Sam wrote: > > So next I stopped my logging app and just run the experiment with > Accerciser monitoring events. When Accerciser is the only app > listening for at-spi events, it gets the same result as I originally > observed: no mouse events are reported. I didn't see this on my system... Accerciser can get all the mouse button events when it is the only AT. Li From Sam.Quiring@windriver.com Mon Dec 15 03:07:52 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 21C327500CC for ; Mon, 15 Dec 2008 03:07:52 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avE365gJ9+di for ; Mon, 15 Dec 2008 03:07:45 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 75B5475009D for ; Mon, 15 Dec 2008 03:07:45 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBF37fcF003072; Sun, 14 Dec 2008 19:07:41 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 14 Dec 2008 19:07:42 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 14 Dec 2008 19:07:40 -0800 Message-ID: In-Reply-To: <4945C2B7.5090401@sun.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [g-a-devel] Interesting event reporting Thread-Index: AcleXg+m7zlJobNnRAi3iR+VciHD+QAAB6Xg References: <4945C2B7.5090401@sun.com> From: "Quiring, Sam" To: X-OriginalArrivalTime: 15 Dec 2008 03:07:42.0098 (UTC) FILETIME=[4B5D4720:01C95E62] Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] Interesting event reporting X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 03:07:52 -0000 Sorry, my statement wasn't clear. What I meant was "when I run that particular experiment Accerciser does not record any mouse events." Accerciser does record mouse events both before and after I run the experiment. I just tried it again and Accerciser did *not* record the mouse click when I ran that experiment. -Sam -----Original Message----- From: Li.Yuan@sun.com [mailto:Li.Yuan@sun.com]=20 Sent: Sunday, December 14, 2008 6:37 PM To: Quiring, Sam Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] Interesting event reporting Quiring, Sam wrote: > =20 > So next I stopped my logging app and just run the experiment with=20 > Accerciser monitoring events. When Accerciser is the only app=20 > listening for at-spi events, it gets the same result as I originally > observed: no mouse events are reported. I didn't see this on my system... Accerciser can get all the mouse button events when it is the only AT. Li From Li.Yuan@Sun.COM Mon Dec 15 05:53:47 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id D556E7500A8 for ; Mon, 15 Dec 2008 05:53:47 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.38 X-Spam-Level: X-Spam-Status: No, score=-5.38 tagged_above=-999 required=2 tests=[AWL=2.219, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G8AD2RhsJ5TP for ; Mon, 15 Dec 2008 05:53:39 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id A391E75006A for ; Mon, 15 Dec 2008 05:53:35 +0000 (GMT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBF5rXRI004945 for ; Mon, 15 Dec 2008 05:53:33 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KBW00J01LMGOA00@mail-apac.sun.com> (original mail from Li.Yuan@Sun.COM) for gnome-accessibility-devel@gnome.org; Mon, 15 Dec 2008 13:53:33 +0800 (SGT) Received: from [129.158.217.85] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KBW0051CLP8M5N1@mail-apac.sun.com>; Mon, 15 Dec 2008 13:53:33 +0800 (SGT) Date: Mon, 15 Dec 2008 13:53:02 +0800 From: Li Yuan In-reply-to: Sender: Li.Yuan@Sun.COM To: "Quiring, Sam" Message-id: <4945F0BE.5010907@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 2.0.0.18 (X11/20081125) Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] registering/deregistering event listeners X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 05:53:48 -0000 Quiring, Sam wrote: > Greetings, > > In my app that interfaces to at-spi I have a function that requires > that I listen for a bunch of different event types. During normal > operation of the app I do not need to listen for these events. The > implementation of this function looks like this: > > 1. register the event handlers > 2. wait for the user to do his thing > 3. deregister the event handlers > > After a few executions of this function (3..6), it dies during step 1: > registering the event handlers. Can you show me the traces of at-spi-registryd and your application? Li > In fact the entire GNOME desktop locks up and I'm forced to power > cycle the machine to get control back. (Is there an easier/cleaner > way to restart GNOME?). > > During app initialization I create the event listeners using > SPI_createAccessibleEventListener() and > SPI_createAccessibleDeviceListener(). My app assumes that once these > listeners are created it can register and deregister them as event > listeners as many times as it wants. Is that correct? > > The code implements deregistering the non-device event listeners using > SPI_derefisterGlobalEventListenerAll() -- I don't know if that matters. > > Any help would be appreciated. > > -Sam > ------------------------------------------------------------------------ > > _______________________________________________ > Gnome-accessibility-devel mailing list > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > From Jeff.Cai@Sun.COM Mon Dec 15 11:26:22 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 4A1A775006A for ; Mon, 15 Dec 2008 11:26:22 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.18 X-Spam-Level: X-Spam-Status: No, score=-5.18 tagged_above=-999 required=2 tests=[AWL=2.419, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJSMtE1oTzer for ; Mon, 15 Dec 2008 11:26:14 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id 7176B7500EA for ; Mon, 15 Dec 2008 11:26:06 +0000 (GMT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBFBQ3oO029542 for ; Mon, 15 Dec 2008 11:26:04 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KBX00801115EX00@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) for gnome-accessibility-devel@gnome.org; Mon, 15 Dec 2008 19:26:03 +0800 (SGT) Received: from [129.158.217.199] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KBX003SY13E7M64@mail-apac.sun.com>; Mon, 15 Dec 2008 19:26:03 +0800 (SGT) Date: Mon, 15 Dec 2008 19:20:52 +0800 From: Jeff Cai In-reply-to: Sender: Jeff.Cai@Sun.COM To: "Quiring, Sam" Message-id: <49463D94.6090307@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] AccessibleDeviceEventMask and SPI_registerDeviceEventListener() X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 11:26:22 -0000 Quiring, Sam wrote: > Greetings, > > I have this call in my app: > > #define BUTTON_EVENTS (SPI_BUTTON_PRESSED | SPI_BUTTON_RELEASED) > SPI_registerDeviceEventListener(mouse_device_listener, > BUTTON_EVENTS, 0); > My read of the documentation, > http://library.gnome.org/devel/at-spi-cspi/stable/at-spi-cspi-Registry-queries.html#SPI-registerDeviceEventListener, > is that my listener should receive all button_press and button_release > events. Most runs of my application never receive any button_release > events. Sometimes the app receives 1 button_release. I have no log > at this time that shows more than 1 button_release. > > On the other hand, I believe I am receiving the correct amount of > button_pressed events. > > Are there any known bugs in this area? Have you run the test program under at-spi/test/event-listener-test.c? Does the test work well? > > -Sam > > > ------------------------------------------------------------------------ > > _______________________________________________ > Gnome-accessibility-devel mailing list > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > From Jeff.Cai@Sun.COM Mon Dec 15 11:31:00 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 77A827500F6 for ; Mon, 15 Dec 2008 11:31:00 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.19 X-Spam-Level: X-Spam-Status: No, score=-5.19 tagged_above=-999 required=2 tests=[AWL=2.409, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBNSsGjMdVrZ for ; Mon, 15 Dec 2008 11:30:51 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id 2FC5075006A for ; Mon, 15 Dec 2008 11:30:50 +0000 (GMT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBFBUmql029717 for ; Mon, 15 Dec 2008 11:30:48 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KBX0010116E7000@mail-apac.sun.com> (original mail from Jeff.Cai@Sun.COM) for gnome-accessibility-devel@gnome.org; Mon, 15 Dec 2008 19:30:48 +0800 (SGT) Received: from [129.158.217.199] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KBX003BK1BB3F32@mail-apac.sun.com>; Mon, 15 Dec 2008 19:30:48 +0800 (SGT) Date: Mon, 15 Dec 2008 19:25:37 +0800 From: Jeff Cai In-reply-to: <9d0602eb0812121304o17fae9f6r8dbc0934aa361e45@mail.gmail.com> Sender: Jeff.Cai@Sun.COM To: Nagappan A Message-id: <49463EB1.5090601@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT References: <9d0602eb0812121304o17fae9f6r8dbc0934aa361e45@mail.gmail.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Cc: gnome-accessibility-devel@gnome.org, "Quiring, Sam" Subject: Re: [g-a-devel] AccessibleDeviceEventMask and SPI_registerDeviceEventListener() X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 11:31:00 -0000 Hi, Nagappan Will CSPI support D-BUS later after we migrate from CORBA to D-BUS? Or CSPI will be EOLed? If an AT program is written in C, how could it use the interface provided by pyatspi? Jeff Nagappan A wrote: > Hi Sam, > > 2008/12/12 Quiring, Sam > > > Greetings, > > I have this call in my app: > > #define BUTTON_EVENTS (SPI_BUTTON_PRESSED | SPI_BUTTON_RELEASED) > SPI_registerDeviceEventListener(mouse_device_listener, > BUTTON_EVENTS, 0); > My read of the documentation, > http://library.gnome.org/devel/at-spi-cspi/stable/at-spi-cspi-Registry-queries.html#SPI-registerDeviceEventListener, > is that my listener should receive all button_press and > button_release events. Most runs of my application never receive > any button_release events. Sometimes the app receives 1 > button_release. I have no log at this time that shows more than 1 > button_release. > > On the other hand, I believe I am receiving the correct amount of > button_pressed events. > > > The events generated in CSPI is not reliable as compared to the > pyatspi. If possible, I recommend to use pyatspi. Also another > advantage will be, when we move to DBus from CORBA, as of now we don't > have CSPI for DBus based implementation. Nagappan > > Thanks > Nagappan > > > Are there any known bugs in this area? > > -Sam > > > > _______________________________________________ > Gnome-accessibility-devel mailing list > Gnome-accessibility-devel@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > > > > > -- > Linux Desktop (GUI Application) Testing Project - > http://ldtp.freedesktop.org > http://nagappanal.blogspot.com > ------------------------------------------------------------------------ > > _______________________________________________ > Gnome-accessibility-devel mailing list > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > From William.Walker@Sun.COM Mon Dec 15 14:55:27 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id DC4E0750120 for ; Mon, 15 Dec 2008 14:55:27 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.737 X-Spam-Level: X-Spam-Status: No, score=-5.737 tagged_above=-999 required=2 tests=[AWL=1.862, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 9, (distance 12, link: ethernet/modem), [192.18.98.36] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rsGTexxbeuG2 for ; Mon, 15 Dec 2008 14:55:19 +0000 (GMT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by menubar.gnome.org (Postfix) with ESMTP id 03E9B75006A for ; Mon, 15 Dec 2008 14:55:18 +0000 (GMT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBFEtH5F022687 for ; Mon, 15 Dec 2008 14:55:17 GMT Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBX006019Y16A00@mail-amer.sun.com> (original mail from William.Walker@Sun.COM) for gnome-accessibility-devel@gnome.org; Mon, 15 Dec 2008 07:55:17 -0700 (MST) Received: from [129.148.9.94] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBX003L4ARUHO70@mail-amer.sun.com>; Mon, 15 Dec 2008 07:55:07 -0700 (MST) Date: Mon, 15 Dec 2008 09:55:06 -0500 From: Willie Walker In-reply-to: <49463EB1.5090601@sun.com> Sender: William.Walker@Sun.COM To: Jeff Cai Message-id: <49466FCA.8090801@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <9d0602eb0812121304o17fae9f6r8dbc0934aa361e45@mail.gmail.com> <49463EB1.5090601@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Cc: gnome-accessibility-devel@gnome.org, "Quiring, Sam" Subject: Re: [g-a-devel] AccessibleDeviceEventMask and SPI_registerDeviceEventListener() X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: William.Walker@Sun.COM List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 14:55:28 -0000 Hi Jeff an everyone: The AT-SPI/D-Bus work is being tracked at http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus, and it includes a plan to migrate CSPI to D-Bus. IMO, doing this work in Python is a lot easier than doing it in C, so that's why we're seeing more and more projects on the assistive technology and testing side moving from the C bindings to the Python bindings. Hope this helps, Will On 12/15/08 06:25, Jeff Cai wrote: > Hi, Nagappan > > Will CSPI support D-BUS later after we migrate from CORBA to D-BUS? Or > CSPI will be EOLed? > > If an AT program is written in C, how could it use the interface > provided by pyatspi? > > Jeff > > Nagappan A wrote: >> Hi Sam, >> >> 2008/12/12 Quiring, Sam > > >> >> Greetings, >> I have this call in my app: >> #define BUTTON_EVENTS (SPI_BUTTON_PRESSED | >> SPI_BUTTON_RELEASED) >> SPI_registerDeviceEventListener(mouse_device_listener, >> BUTTON_EVENTS, 0); >> My read of the documentation, >> >> http://library.gnome.org/devel/at-spi-cspi/stable/at-spi-cspi-Registry-queries.html#SPI-registerDeviceEventListener, >> >> is that my listener should receive all button_press and >> button_release events. Most runs of my application never receive >> any button_release events. Sometimes the app receives 1 >> button_release. I have no log at this time that shows more than 1 >> button_release. >> On the other hand, I believe I am receiving the correct >> amount of >> button_pressed events. >> >> >> The events generated in CSPI is not reliable as compared to the >> pyatspi. If possible, I recommend to use pyatspi. Also another >> advantage will be, when we move to DBus from CORBA, as of now we don't >> have CSPI for DBus based implementation. > Nagappan > > > >> >> Thanks >> Nagappan >> >> Are there any known bugs in this area? >> -Sam >> >> _______________________________________________ >> Gnome-accessibility-devel mailing list >> Gnome-accessibility-devel@gnome.org >> >> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel >> >> >> >> >> -- >> Linux Desktop (GUI Application) Testing Project - >> http://ldtp.freedesktop.org >> http://nagappanal.blogspot.com >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Gnome-accessibility-devel mailing list >> Gnome-accessibility-devel@gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel >> > > _______________________________________________ > Gnome-accessibility-devel mailing list > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel From Sam.Quiring@windriver.com Mon Dec 15 16:26:26 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 0D0AC750131 for ; Mon, 15 Dec 2008 16:26:26 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPD41e-Sqi1r for ; Mon, 15 Dec 2008 16:26:18 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 021A4750129 for ; Mon, 15 Dec 2008 16:26:15 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBFGQDYP027221; Mon, 15 Dec 2008 08:26:13 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 Dec 2008 08:26:13 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 15 Dec 2008 08:26:12 -0800 Message-ID: In-Reply-To: <4945F0BE.5010907@sun.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [g-a-devel] registering/deregistering event listeners Thread-Index: AcleeYRqbHxaaCHWTF+fXBBKnUwd8wAV5GvQ References: <4945F0BE.5010907@sun.com> From: "Quiring, Sam" To: X-OriginalArrivalTime: 15 Dec 2008 16:26:13.0774 (UTC) FILETIME=[D8F2DAE0:01C95ED1] Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] registering/deregistering event listeners X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 16:26:26 -0000 Hello Li, I am working on fixing a race condition that I discovered just after reporting the problem below. When I get the race condition resolved, I'll see if I can reproduce the problem reported below. -Sam -----Original Message----- From: Li.Yuan@sun.com [mailto:Li.Yuan@sun.com]=20 Sent: Sunday, December 14, 2008 9:53 PM To: Quiring, Sam Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] registering/deregistering event listeners Quiring, Sam wrote: > Greetings, > =20 > In my app that interfaces to at-spi I have a function that requires=20 > that I listen for a bunch of different event types. During normal=20 > operation of the app I do not need to listen for these events. The=20 > implementation of this function looks like this: > =20 > 1. register the event handlers > 2. wait for the user to do his thing > 3. deregister the event handlers > =20 > After a few executions of this function (3..6), it dies during step 1: > registering the event handlers. Can you show me the traces of at-spi-registryd and your application? Li > In fact the entire GNOME desktop locks up and I'm forced to power=20 > cycle the machine to get control back. (Is there an easier/cleaner=20 > way to restart GNOME?). > =20 > During app initialization I create the event listeners using > SPI_createAccessibleEventListener() and=20 > SPI_createAccessibleDeviceListener(). My app assumes that once these=20 > listeners are created it can register and deregister them as event=20 > listeners as many times as it wants. Is that correct? > =20 > The code implements deregistering the non-device event listeners using > SPI_derefisterGlobalEventListenerAll() -- I don't know if that matters. > =20 > Any help would be appreciated. > =20 > -Sam > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Gnome-accessibility-devel mailing list=20 > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > =20 From Sam.Quiring@windriver.com Mon Dec 15 18:47:07 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 7C3F1750147 for ; Mon, 15 Dec 2008 18:47:07 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -4.599 X-Spam-Level: X-Spam-Status: No, score=-4.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o17Aas6SYygg for ; Mon, 15 Dec 2008 18:46:59 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 401CF75030D for ; Mon, 15 Dec 2008 18:45:43 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBFIjdmf006012; Mon, 15 Dec 2008 10:45:39 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 Dec 2008 10:45:39 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 15 Dec 2008 10:45:38 -0800 Message-ID: In-Reply-To: <49463D94.6090307@sun.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [g-a-devel] AccessibleDeviceEventMaskand SPI_registerDeviceEventListener() Thread-Index: AcleqEJHtmdf3dJrRW2U9yS1UebIJQANHAoA References: <49463D94.6090307@sun.com> From: "Quiring, Sam" To: "Jeff Cai" X-OriginalArrivalTime: 15 Dec 2008 18:45:39.0902 (UTC) FILETIME=[538CADE0:01C95EE5] Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] AccessibleDeviceEventMaskand SPI_registerDeviceEventListener() X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 18:47:07 -0000 Cai, Jeff wrote: > Have you run the test program under at-spi/test/event-listener-test.c? > Does the test work well? I have at-spi-1.24.0. I tried installing it by running "./configure", but I got this: configure: error: Your intltool is too old. You need intltool 0.40.0 or later. I downloaded intltool 0.40 and tried installing that, but got a syntax error in the installation. So I gave up. I am working on fixing a race condition that I discovered after reporting the problem below. When I get the race condition resolved, I'll see if I can reproduce the problem reported below. -Sam -----Original Message----- From: gnome-accessibility-devel-bounces@gnome.org [mailto:gnome-accessibility-devel-bounces@gnome.org] On Behalf Of Jeff Cai Sent: Monday, December 15, 2008 3:21 AM To: Quiring, Sam Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] AccessibleDeviceEventMaskand SPI_registerDeviceEventListener() Quiring, Sam wrote: > Greetings, > =20 > I have this call in my app: > =20 > #define BUTTON_EVENTS (SPI_BUTTON_PRESSED | SPI_BUTTON_RELEASED) > SPI_registerDeviceEventListener(mouse_device_listener, > BUTTON_EVENTS, 0); > My read of the documentation, > http://library.gnome.org/devel/at-spi-cspi/stable/at-spi-cspi-Registry > -queries.html#SPI-registerDeviceEventListener, > is that my listener should receive all button_press and button_release > events. Most runs of my application never receive any button_release=20 > events. Sometimes the app receives 1 button_release. I have no log=20 > at this time that shows more than 1 button_release. > =20 > On the other hand, I believe I am receiving the correct amount of=20 > button_pressed events. > =20 > Are there any known bugs in this area? Have you run the test program under at-spi/test/event-listener-test.c?=20 Does the test work well? > =20 > -Sam > =20 > =20 > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Gnome-accessibility-devel mailing list=20 > Gnome-accessibility-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel > =20 _______________________________________________ Gnome-accessibility-devel mailing list Gnome-accessibility-devel@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel From Sam.Quiring@windriver.com Mon Dec 15 20:54:11 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id F2A60750115 for ; Mon, 15 Dec 2008 20:54:10 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -4.442 X-Spam-Level: X-Spam-Status: No, score=-4.442 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqV-bvPKdHyg for ; Mon, 15 Dec 2008 20:54:03 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 7C15875007E for ; Mon, 15 Dec 2008 20:54:02 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBFKs1Pf006059 for ; Mon, 15 Dec 2008 12:54:01 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 Dec 2008 12:54:01 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C95EF7.41A3D1FC" Date: Mon, 15 Dec 2008 12:54:00 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to tell if a button has been clicked? Thread-Index: Acle90Fqo15vEiyRQeK8MsJ4/p9NUA== From: "Quiring, Sam" To: X-OriginalArrivalTime: 15 Dec 2008 20:54:01.0431 (UTC) FILETIME=[4204BE70:01C95EF7] Subject: [g-a-devel] How to tell if a button has been clicked? X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 20:54:11 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C95EF7.41A3D1FC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, =20 Suppose the user of the Gnome desktop does this: =20 1. runs and app with a button on it 2. moves the mouse on top of the button 3. presses the left mouse button down on the button 4. moves the mouse off the button 5. releases the left mouse button =20 When you do this, the button is not clicked, that is, the signal handler in the app for "clicked" is not called. =20 What at-spi event sequence would reveal this to an accessibility application? The best solution I've come up with so far is to record the bounding box of the widget on which the mouse was pressed and, in the button-release handler, check to see if the mouse is still inside that bounding box. =20 Is there a better way? =20 I just finished adding event handlers for Gtk:GtkWidget:button-press-event and Gtk:GtkWidget:button-release-event. In the above situation my app gets both events and even though the mouse is no longer on the button when the user releases the mouse button, the Gtk:GtkWidget:button-release-event source object is the button. Is this a bug? =20 -Sam ------_=_NextPart_001_01C95EF7.41A3D1FC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

Suppose the user of=20 the Gnome desktop does this:

1. = runs and app with=20 a button on it

2. = moves the mouse=20 on top of the button

3. = presses the left=20 mouse button down on the button

4. = moves the mouse=20 off the button

5. = releases the left=20 mouse button

When = you do this,=20 the button is not clicked, that is, the signal handler in the app for = "clicked"=20 is not called.

What = at-spi event=20 sequence would reveal this to an accessibility application? = The best=20 solution I've come up with so far is to record the bounding box of the = widget on=20 which the mouse was pressed and, in the button-release handler, check to = see if=20 the mouse is still inside that bounding box.

Is = there a better=20 way?

I just = finished=20 adding event handlers for=20 Gtk:GtkWidget:button-press-event and=20 Gtk:GtkWidget:button-release-event. = In the=20 above situation my app gets both events and even though the mouse = is no=20 longer on the button when the user releases the mouse=20 button, the Gtk:GtkWidget:button-release-event= source=20 object is the button. Is this a bug?

-Sam

------_=_NextPart_001_01C95EF7.41A3D1FC-- From Li.Yuan@Sun.COM Tue Dec 16 03:00:16 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 7FEB5750135 for ; Tue, 16 Dec 2008 03:00:16 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.309 X-Spam-Level: X-Spam-Status: No, score=-5.309 tagged_above=-999 required=2 tests=[AWL=2.134, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wB8cdqBKMLcw for ; Tue, 16 Dec 2008 03:00:09 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id B784A7501A9 for ; Tue, 16 Dec 2008 03:00:03 +0000 (GMT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBG2xwRa025452 for ; Tue, 16 Dec 2008 03:00:01 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KBY00I018BI2A00@mail-apac.sun.com> (original mail from Li.Yuan@Sun.COM) for gnome-accessibility-devel@gnome.org; Tue, 16 Dec 2008 10:59:58 +0800 (SGT) Received: from [129.158.217.85] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KBY003AL8BX7M68@mail-apac.sun.com>; Tue, 16 Dec 2008 10:59:58 +0800 (SGT) Date: Tue, 16 Dec 2008 10:59:26 +0800 From: Li Yuan In-reply-to: Sender: Li.Yuan@Sun.COM To: "Quiring, Sam" Message-id: <4947198E.6010906@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 2.0.0.18 (X11/20081126) Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] How to tell if a button has been clicked? X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Dec 2008 03:00:16 -0000 Quiring, Sam wrote: > Greetings, > > Suppose the user of the Gnome desktop does this: > > 1. runs and app with a button on it > 2. moves the mouse on top of the button > 3. presses the left mouse button down on the button > 4. moves the mouse off the button > 5. releases the left mouse button > > When you do this, the button is not clicked, that is, the signal > handler in the app for "clicked" is not called. > > What at-spi event sequence would reveal this to an accessibility > application? The best solution I've come up with so far is to record > the bounding box of the widget on which the mouse was pressed and, in > the button-release handler, check to see if the mouse is still inside > that bounding box. Yes, that's the way I am thinking of. > > Is there a better way? > > I just finished adding event handlers for > */Gtk:GtkWidget:button-press-event/* and > */Gtk:GtkWidget:button-release-event/*. In the above situation my app > gets both events and even though the mouse is no longer on the button > when the user releases the mouse > button, the *Gtk:GtkWidget:button-release-event* source object is the > button. Is this a bug? We probably need to discuss this in Gtk+ list. Li From mark.doffman@codethink.co.uk Thu Dec 18 10:20:35 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 6FDD27500B4 for ; Thu, 18 Dec 2008 10:20:35 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599] X-Amavis-OS-Fingerprint: Linux 2.6, seldom 2.4 (older, 4) (up: 9325 hrs), (distance 15, link: ethernet/modem), [208.78.103.131] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A6urn5CKF015 for ; Thu, 18 Dec 2008 10:20:29 +0000 (GMT) Received: from mail.codethink.co.uk (floopily.codethink.co.uk [208.78.103.131]) by menubar.gnome.org (Postfix) with ESMTP id 2D8BA7500EC for ; Thu, 18 Dec 2008 10:20:26 +0000 (GMT) Received: from [192.168.0.3] (82-69-7-91.dsl.in-addr.zen.co.uk [82.69.7.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.codethink.co.uk (Postfix) with ESMTPSA id 7E0B8C089C for ; Thu, 18 Dec 2008 10:20:24 +0000 (GMT) Message-ID: <494A23E7.80306@codethink.co.uk> Date: Thu, 18 Dec 2008 10:20:23 +0000 From: Mark Doffman User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: gnome-accessibility-devel@gnome.org References: In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [g-a-devel] AccessibleDeviceEventMask and, SPI_registerDeviceEventListener() X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2008 10:20:35 -0000 Hi Jeff, > Will CSPI support D-BUS later after we migrate from CORBA to D-BUS? Or > CSPI will be EOLed? > > If an AT program is written in C, how could it use the interface > provided by pyatspi? When moving to D-Bus we have no intention of EOLing cspi. We need all the ATs currently written using the library to keep going. Its true that at the moment cspi is out-of-action in the D-Bus project. But Mike Gorse has recently been putting patches in, so it may be up and running soon. Two cents on an old issue... My personal preference would be to use pyatspi for new ATs. The interface is better, and who wants to code in 'C' anyway. :) Thanks Mark From Sam.Quiring@windriver.com Tue Dec 30 15:54:23 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 6E35575000A for ; Tue, 30 Dec 2008 15:54:23 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=2 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHKOfqtpA54b for ; Tue, 30 Dec 2008 15:54:16 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 106E2750006 for ; Tue, 30 Dec 2008 15:54:13 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBUFsB9D011150 for ; Tue, 30 Dec 2008 07:54:11 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 30 Dec 2008 07:54:12 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C96A96.DBC3A69D" X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 30 Dec 2008 07:54:10 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Dangling pointers when an Accessible * window is killed Thread-Index: AclqltsDYABlQBcnRk2qDjAU7gpfTw== From: "Quiring, Sam" To: X-OriginalArrivalTime: 30 Dec 2008 15:54:12.0665 (UTC) FILETIME=[DC132290:01C96A96] Subject: [g-a-devel] Dangling pointers when an Accessible * window is killed X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2008 15:54:23 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C96A96.DBC3A69D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, =20 We were running an experiment where our app has an Accessible * pointer to a window. If the window is closed and the app then tries to use the Accessible * pointer, the at-spi system gets a segfault. Is there a good way to test the validity of an Accessible * pointer so we can avoid the segfault? Or is segfault the normal at-spi way of telling the accessible application that a window has disappeared? =20 -Sam =20 ------_=_NextPart_001_01C96A96.DBC3A69D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

We = were running an=20 experiment where our app has an Accessible * pointer to a window. = If the=20 window is closed and the app then tries to use the Accessible=20 * pointer, the at-spi system gets a segfault. Is there a good = way to=20 test the validity of an Accessible * pointer so we can avoid the = segfault? =20 Or is segfault the normal at-spi way of telling the accessible = application that=20 a window has disappeared?

-Sam

------_=_NextPart_001_01C96A96.DBC3A69D-- From Li.Yuan@Sun.COM Wed Dec 31 02:47:37 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 8202475000A for ; Wed, 31 Dec 2008 02:47:37 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -5.393 X-Spam-Level: X-Spam-Status: No, score=-5.393 tagged_above=-999 required=2 tests=[AWL=2.206, BAYES_00=-2.599, L_P0F_Unix=-1, RCVD_IN_DNSWL_MED=-4] X-Amavis-OS-Fingerprint: Solaris 10 (beta), (distance 19, link: ethernet/modem), [192.18.19.7] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFRB8iqhtgD0 for ; Wed, 31 Dec 2008 02:47:31 +0000 (GMT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by menubar.gnome.org (Postfix) with ESMTP id E5D5F7501A1 for ; Wed, 31 Dec 2008 02:47:25 +0000 (GMT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBV2l9A2019205 for ; Wed, 31 Dec 2008 02:47:22 GMT Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0KCP00C01ZNNT500@mail-apac.sun.com> (original mail from Li.Yuan@Sun.COM) for gnome-accessibility-devel@gnome.org; Wed, 31 Dec 2008 10:47:09 +0800 (SGT) Received: from [129.158.217.197] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KCP0037SZQK3FGI@mail-apac.sun.com>; Wed, 31 Dec 2008 10:47:09 +0800 (SGT) Date: Wed, 31 Dec 2008 10:46:23 +0800 From: Li Yuan In-reply-to: Sender: Li.Yuan@Sun.COM To: "Quiring, Sam" Message-id: <495ADCFF.5080704@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: User-Agent: Thunderbird 2.0.0.18 (X11/20081125) Cc: gnome-accessibility-devel@gnome.org Subject: Re: [g-a-devel] Dangling pointers when an Accessible * window is killed X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2008 02:47:37 -0000 Quiring, Sam wrote: > Greetings, > > We were running an experiment where our app has an Accessible * > pointer to a window. Your app acts as an AT, right? > If the window is closed and the app then tries to use the Accessible > * pointer, the at-spi system gets a segfault. How did you get the pointer? Did you ref it? If so there could be a bug in GAIL. > Is there a good way to test the validity of an Accessible * pointer so > we can avoid the segfault? Or is segfault the normal at-spi way of > telling the accessible application that a window has disappeared? The object should not be finalized if you still have reference. Regards, Li From Sam.Quiring@windriver.com Wed Dec 31 22:21:03 2008 Return-Path: X-Original-To: gnome-accessibility-devel@gnome.org Delivered-To: gnome-accessibility-devel@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 410A375007C for ; Wed, 31 Dec 2008 22:21:03 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.184 X-Spam-Level: X-Spam-Status: No, score=-2.184 tagged_above=-999 required=2 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, L_P0F_Unix=-1, RCVD_IN_DNSWL_LOW=-1] X-Amavis-OS-Fingerprint: Solaris 9, (distance 15, link: ethernet/modem), [147.11.1.11] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aV01+jCnuRe for ; Wed, 31 Dec 2008 22:20:56 +0000 (GMT) Received: from mail.wrs.com (mail.windriver.com [147.11.1.11]) by menubar.gnome.org (Postfix) with ESMTP id 891DB750065 for ; Wed, 31 Dec 2008 22:20:56 +0000 (GMT) Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id mBVMKqOZ023893 for ; Wed, 31 Dec 2008 14:20:52 -0800 (PST) Received: from ala-mail02.corp.ad.wrs.com ([147.11.57.56]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Dec 2008 14:20:52 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C96B96.0A7975AA" X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 31 Dec 2008 14:20:52 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Which window is on top? Thread-Index: Aclri4xEh1ZBPArzRCW7+zyLigifSw== From: "Quiring, Sam" To: X-OriginalArrivalTime: 31 Dec 2008 22:20:52.0906 (UTC) FILETIME=[0AE8B8A0:01C96B96] Subject: [g-a-devel] Which window is on top? X-BeenThere: gnome-accessibility-devel@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: "Technical discussions and patches for at-spi, gail, and ATs" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2008 22:21:03 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C96B96.0A7975AA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, =20 I have multiple apps running with windows layered on top of windows. The user moves the mouse to a point that, as you drill down, is in multiple different windows. I cannot find a way to figure out what window is on top nor the zorder relationship of the windows. Every GUI item on every window, regardless if it is totally obscured, partially visible, or totally visible shows up as STATE_VISIBLE and STATE_SHOWING. Once my app finds the innermost object containing the mouse it displays the complete parent tree. Every parent is also STATE_VISIBLE and STATE_SHOWING. I've tried Accessible_getMDIZOrder, but it returns 0 all the time except for two cases of icons on the desktop. =20 If two windows cover the same pixel on the desktop, how can I figure out which one is higher in the zorder and which is lower? If I've overlooked something really obvious, I apologize. =20 -Sam =20 PS: Just in case Accessible_getMDIZOrder is supposed to be the answer, here's my code that almost always returns 0: =20 short getZOrder(Accessible *accessibleObject) { if(Accessible_isComponent(accessibleObject)) { AccessibleComponent *aComponent =3D Accessible_getComponent(accessibleObject); short zo =3D AccessibleComponent_getMDIZOrder(aComponent); AccessibleComponent_unref(aComponent); return zo; } return -2; // for applications } ------_=_NextPart_001_01C96B96.0A7975AA Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

I have = multiple apps=20 running with windows layered on top of windows. The user moves the = mouse=20 to a point that, as you drill down, is in multiple different = windows. =20 I cannot find a way to figure out what window is on top nor the zorder=20 relationship of the windows. Every GUI item on every window, = regardless if=20 it is totally obscured, partially visible, or totally visible shows up = as=20 STATE_VISIBLE and STATE_SHOWING. Once my app finds the innermost = object=20 containing the mouse it displays the complete parent tree. Every = parent is=20 also STATE_VISIBLE and STATE_SHOWING. I've tried = Accessible_getMDIZOrder,=20 but it returns 0 all the time except for two cases of icons on = the=20 desktop.

If two = windows cover=20 the same pixel on the desktop, how can I figure out which one is higher = in the=20 zorder and which is lower? If I've overlooked something really = obvious, I=20 apologize.

-Sam

PS: = Just in case=20 Accessible_getMDIZOrder is supposed to be the answer, here's my code = that almost=20 always returns 0:

short=20 getZOrder(Accessible *accessibleObject)
{
   =20 if(Accessible_isComponent(accessibleObject))=20 {
        AccessibleComponent = *aComponent=20 =3D =20 Accessible_getComponent(accessibleObject);
    &nb= sp;  =20 short zo =3D=20 AccessibleComponent_getMDIZOrder(aComponent);
    =    =20 AccessibleComponent_unref(aComponent);
     &= nbsp; =20 return zo;
    }
    return = -2; // for=20 applications
}

------_=_NextPart_001_01C96B96.0A7975AA--