To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=88069





------- Additional comments from williewal...@openoffice.org Fri Mar 27 
13:26:55 +0000 2009 -------
@od - thank you.  I'm less interested in the actual binary and more interested
in which version of libatk-bridge the changes were made in.  This is useful to
me so I know where we'll stand in terms of integration.  I was wondering if you
knew before I went digging.

>From your response, I'm guessing you don't know.  :-)  So, I went digging
because this kind of cross reference and dependency is useful to have written
down.  The GNOME bug that was used to track this is as follows:

http://bugzilla.gnome.org/show_bug.cgi?id=567706

The relevant GNOME svn revisions are as follows, which seem to indicate it went
into GNOME 2.25.5 (and hence GNOME 2.26.0):

http://svn.gnome.org/viewvc/at-spi?view=revision&revision=1149
http://svn.gnome.org/viewvc/at-spi?view=revision&revision=1150

I don't see any commits for the gnome-2-24 branch.  I also checked the JDS
svn.opensolaris.org/svn/jds/spec-files/branches/gnome-2-24 patches to see if
there were any downstream fixes for OpenSolaris.  None have been done.

So, it looks as though one will need GNOME 2.26.0 or better along with some
version of OOo (3.1?) in order to get this functionality.

Thanks!

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org
For additional commands, e-mail: issues-h...@sw.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to