Mick, First please open a bug at http://bugs.freestandards.org/. You can
document what changes you want to make in the bug report and the community
can discuss it in the bug log. We would typically discuss code changes by
having you attach a patch file to the bug, but I have not gotten that far
in setting up a change process for IA2. I will ask about which patch tool
is best to use for the BZR system that holds the IDL on the Linux
Foundation servers. Once we know that then you can attach a patch to the
bug.
p.s. I am on vacation for the rest of this month so I will be slow in
responding.
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G
"Michael Curran" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
12/10/2007 10:18 PM
To
<[EMAIL PROTECTED]>
cc
Subject
[Accessibility-ia2] state, role and event constants not included in
library from IDL
Hi Pete and all,
I was wondering if it was at all possible to re-think the way the
IAccessible2Lib part of the IDL was written? (it has a library block and
inside it includes all the interfaces).
This is fine for making the interfaces be included in the library, however
constants such as states, roles and events are not included. For some
reason
all the enums are included... I guess some how IDL interpreters can see
that
the enums are dependencies for something, but those other constants are
not.
The reason this is annoying for me is that I convert the IDL to a tlb and
then convert the tlb to python code. All the interfaces and enums are
included, but the roles, states and events are not, so I need to manually
write them in another python file myself. This is fine, but if IA2 ever
changes, I'll have a hard time keeping them up to date.
I would suggest that another idl file is written that only contains the
library block, and inside include statements including all the other IDL
files.
I *think* this would work.
I can try creating that file if you like, though I would like to know your
thoughts on it anyway.
Thanks
Mick
----- Original Message -----
From: Pete Brunet
To: Aaron M Leventhal ; Xing X Li ; [EMAIL PROTECTED] ;
[EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Tuesday, December 11, 2007 2:19 PM
Subject: Re: Misspelling of event name in AccessibleEvent.idl
Aaron, I also noticed that recently. I can add constants so the correct
ones
can be used.
IA2_STATE_MANAGES_DESCENDANTS
IA2_EVENT_ACTIVE_DESCENDANT_CHANGED
If I find that someone is using the curent ones I can leave the old ones
there too (using the same constant values).
Xing, Rob, Bill, and Mick, Are any of you using the misspelled constants
IA2_STATE_MANAGES_DECENDANTS
IA2_EVENT_ACTIVE_DECENDENT_CHANGED
Pete Brunet
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G
Aaron M Leventhal/Cambridge/IBM
12/10/2007 09:50 AM
To Pete Brunet/Austin/[EMAIL PROTECTED]
cc
Subject Misspelling of event name in AccessibleEvent.idl
34 /** The active descendant of a component has changed. The active
descendant
35 is used in objects with transient children.
36 */
37 IA2_EVENT_ACTIVE_DECENDENT_CHANGED,
38
It's missing an "s" and uses "ent" at the end. It's inconsistent both with
ATK/AT-SPI and the comment aboive it. I suggest using the spelling in the
comment and ATK/AT-SPI.
- Aaron
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
