Hi Felix,
Sorry, that was my failure, it looks like I still had focus in the
database report document itself. I can reproduce the problem now. :)
The problem seems to be that the frame of the source browser has no
dispatch interceptor. Thus the default close mechanics of the child
frame is activated. Unfortunately the default mechanics has already a
hack required by the database component inside some times ago.
The planned solution currently is to create a general dispatch
interceptor helper designed for similar scenarios. This interceptor
should intercept the close event and send them to the parent frame
dispatcher. An example of the dispatch interceptor can be found in
embeddedobj/source/general/intercept.cxx. It even intercepts already the
three closing event. Based on this interceptor the helper interceptor
should be implemented.
comphelper project is probably a good place to implement the helper. So
you can probably start to investigate the example and write the
implementation. The questions are as always welcome.
After the mentioned solution is integrated the mentioned hack seems not
to be necessary any more, and can be removed probably.
Best regards,
Mikhail.
On 11/19/08 19:58, Mikhail Voitenko wrote:
Hi Felix,
during investigation of the source browser frame behavior, I have
recognized that I just can not reproduce the scenario from the issue
i93473 neither in OOO300_m11 nor in DEV300_m35. In which version could
you reproduce the issue?
Thanks,
Mikhail.
PS: Please do not forget to attach the patch for the issue i78753.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
