To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103859
------- Additional comments from npo...@openoffice.org Fri Mar 26 15:22:51 +0000 2010 ------- >no true I think, I would suspect ab71 ( and my vba fake event stuff ) is the >real culprit so, after eventually getting a build for this cws ( after the resync ) and doing some debugging it seems this is not anything to do with this cws ( or ab71 ), this is an issue with the excel filter ( not sure since when but I reproduced with 3.2 rc5 ) What is happening is the filter is importing a macro binding for a control, even if the filter fails to find the macro it still sets up the binding. You can recreate the same error by making a macro binding for a button and afterwards delete the macro. Anyway in imo this is no big problem --------------------------------------------------------------------- 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...@script.openoffice.org For additional commands, e-mail: issues-h...@script.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
