To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94033
User fs changed the following:
What |Old value |New value
================================================================================
Status|STARTED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Oct 16 13:05:27 +0000
2008 -------
This is a regression of the fix for issue 87728. There, code was added which
calls XTabController.updateTabOrder every time a new control is inserted into
the document view while in alive mode. This was because in some timing-dependent
scenarios, the tabbing order for such controls was not correct.
Now unfortunately when you open a document whose controls are in alive mode from
the beginning, then this means one updateTabOrder call for every control as it
is created, which sums up to a stunning amount of time ...
I fixed this by deferring the updateTabOrder call(s) to the point where all
controls have been created.
Since the fix is for 3.0.1, I needed to use a little hack in some place, which
helped fixing the bug, but is a little bit dirty. Issue 95010 is dedicated to
removing this hack, and replacing it with the proper solution in the DEV300 code
line.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
