GNOME Bugzilla – Bug 440035
Add more information to atk-types.def
Last modified: 2013-08-26 13:09:23 UTC
Some of the generation errors of the form: Could not write virtual accessor method AtkComponent.get_extents: No ArgType for gint* might be resolved by adding to the atk-types.def file. In this case, the solution is currently defined as a manual wrapper. However, others cases exist without wrappers, especially the interface proxies needed to implement atk support for custom widgets. For example: Could not write interface proxy AtkEditableText.set_run_attributes: No ArgType for AtkAttributeSet*
For reference, here are the interface proxies that could not be written. Some of them (e.g. gpointer) probably can't be solved by adding new types alone. Could not write interface proxy AtkComponent.add_focus_handler: No ArgType for AtkFocusHandler Could not write interface proxy AtkDocument.get_document: No ArgType for gpointer Could not write interface proxy AtkEditableText.set_run_attributes: No ArgType for AtkAttributeSet* Could not write interface proxy AtkStreamableContent.get_stream: No ArgType for GIOChannel* Could not write interface proxy AtkTable.get_selected_columns: No ArgType for gint** Could not write interface proxy AtkTable.get_selected_rows: No ArgType for gint** Could not write interface proxy AtkText.get_character_at_offset: No ArgType for gunichar Could not write interface proxy AtkText.get_run_attributes: No ArgType for AtkAttributeSet* Could not write interface proxy AtkText.get_default_attributes: No ArgType for AtkAttributeSet* Could not write interface proxy AtkText.get_range_extents: No ArgType for AtkTextRectangle* Could not write interface proxy AtkText.get_bounded_ranges: No ArgType for AtkTextRange** Could not write interface proxy AtkValue.get_current_value: No ArgType for GValue* Could not write interface proxy AtkValue.get_maximum_value: No ArgType for GValue* Could not write interface proxy AtkValue.get_minimum_value: No ArgType for GValue* Could not write interface proxy AtkValue.set_current_value: No ArgType for const-GValue*
Appears value interface proxies must be written manually to account for GValue types and the fact that AT-SPI only allows for doubles anyways. Opening another bug on this topic.