Hi, Frank Schönheit - Sun Microsystems Germany wrote: > Hi Kai, > >> *Summary* >> -------- >> + com.sun.star.task.XInteractionRequestStringResolver >> + com.sun.star.task.InteractionRequestStringResolver >> >> *Description* >> ------------- >> The css.task.InteractionRequestStringResolver service implemenation >> obtains human readable localized strings from informational >> css.task.XInteractionRequest's. > > Sorry, it is not clear to me how this is intended to be > used/implemented. Could you please kindly elaborate?
Sure. The concrete use case is that simple (plain informational) error messages propagated by css.task.Interactionhandler shall be intercepted and put into a special dialog containing sort of an error log. => product and extension online update. For this, one implements its own interaction handler. This interaction handler's implementation of handle() forwards all incoming interaction requests to css.task.InteractionRequestStringResolver. If the resolver is able to obtain a string for the request -- which is the case if the interaction contains a simple (plain informational) error message - the string is used for whatever the intention was and the request is marked handled by the wrapping interaction handler. In case InteractionRequestStringResolver is not able to obatain a string (non-trivial request like password request..., the requests is passed on to the standard interaction handler. HTH, Kai. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
