GNOME Bugzilla – Bug 546341
[a11y] Goocanvas does not implement children-changed signal
Last modified: 2008-11-10 16:37:40 UTC
From http://blogs.gnome.org/johncarr/2008/08/04/conduit-and-accessibility/ "We use GooCanvas, which is actually already accessible. Each item that is added to the canvas is available to accessibility tools, be it a raw canvas item or a gtk widget. Basic information such as its size and position is exposed without any effort on the part of the application author. Whilst experimenting, I have hit the following limitations:" and "2. GooCanvas doesn’t seem to implement the children-changed signal. In testing this has meant that accerciser is unaware of changes on the canvas, and i’ve needed to keep restarting accerciser." I guess that children-changed should be emitted whenever a child items properties change, such as size, x/y, etc.
The children-changed signal should be emitted when a child item is added or removed from the canvas. I was going to write a patch for this, but had it mentally queued for after my next round of hitting conduit with a stick. If someone wants to help me out here, it would be lovely :-)
Created attachment 115875 [details] [review] First attempt at a patch Here's a first go at a patch. It needs testing though.
Thanks very much for this Damon. I'll roll it in to my system and see what happens.
John, do you have any feedback on that patch?
The patch was applied before GooCanvas 0.11, though it was changed slightly.
Closing because the patch was applied.