From: "Wan, Shuang" <[email protected]> > >Ups, sorry, I understood that you finally were able to solve that on > >your screenshot, at least with the examples. This mean that you were > >able to find the cally examples as a app, but you were not able to see > >the object hierarchy? > > Yes. I am able to find the cally examples as app, but I am not able to see > the object hierarchy. I have read the cally source code and put some debug > message within it. In function cally_group_get_n_children, it prints 3 while > the Accerciser launching. But in the Accerciser Accessiblity Exploer, the > Children of Main Stage is still the 0. Seems I need to track the issue more > deeply, may be to put some debug message in atk, at-spi2-atk and > at-spi2-core. Do you have any good suggestion, or good documents about to atk > like sequence diagram? It will be very great if you could try cally on Moblin > directly:)
Normally, when I testing the hierarchy exposed, I usually use python scripts in dogtail. You could try to do that as well, although as accerciser is failing, probably you would get the same problem (anyway you don't lose anything trying). And it is really strange that the cally functions are returning 3 as the children number but then the accerciser is getting 0. Anyway, after the comments from Sam Quiring I thought that the default SPI is still the bonobo-at-spi, do you really need to use the dbus one? But yes, some day I would need to test cally inside mobling, and more important, using AT-SPI-DBUS. === API ([email protected]) -- To unsubscribe send a mail to [email protected]
