To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=101274
------- Additional comments from dtar...@openoffice.org Fri Apr 24 08:34:19 +0000 2009 ------- dtardon->kso: > IIRC, ucb -> ucbhelper throws an exception in this > case or uses an interaction handler to display an error (if an interaction > handler is present and able to handle this certain interaction request). IMO, > the best approach would be to fix the framework code. I actually thought about it that way (i.e. do the concerned handling at framework level) and even sketched some code, but then decided to do it in ucbhelper. Looks I was wrong, then :( > OTOH, fixing this in ucbhelper only has effect for ucb clients using ucb via > ucbhelper C++ API, not for ucb clients using ucb UNO API directly. Thus, if we > decide that the right place for a fix is not framework, it would be > ucb/source/ucp/*. That will be valid concern, I think. I overlooked that. I'll give it another try. --------------------------------------------------------------------- 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...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
