Cristina Scheau wrote:
Hi Carsten,
On Mon, Aug 10, 2009 at 12:23 PM, Carsten Driesner <[email protected]
wrote:
Cristina Scheau wrote:
Hi Carsten,
Thank you very much for answering me.
Hi Christina,
I tried to give up on docking support and I've chosen the solution with
UNO
dialogs. My dialog with the tree control should be non-modal. If the
current
document window is the parent of my window , my window is not modal . (the
user cannot change the focus window- document).
There is something I don't understand in your last two sentences. For me it
looks like a conflict. If a window is not in modal mode a user CAN change
the focus. E.g. the file dialog always starts in modal mode and you cannot
change focus to the dependent document window.
Sorry, my bad , I intended to write "modal".
If I set the parent to be
the desktop , the two windows are totally independent. In this case I
have
to handle manually every event like closing the window, resizing it etc (
when the user closes the document window I need my small dialog to be
closed too). Is there any other alternative that allows the two windows to
be dependent, but also the focus to be changed?
How do you start the dialog? Please don't use execute() which starts the
dialog in modal mode. You have to use show() otherwise you could see the
described behavior.
I start the dialog with execute() method from XDialog interface. The
XDialog interface doesn't seem to offer a show() method. Is there any other
place where I find it? For now , I create a non-modal dialog , creating a
different window which is invisible and setting this window as Peer for my
dialog. Of course this is a temporary solution because I would need to
handle all the events from the document window.
Hi Christina,
Sorry for the late answer but I have tried to look for a solution.
Unfortunately I wasn't able to find anything what can help you here. The
object you get via the DialogProvider service just implements XDialog
and XTopWindow neither implements anything that you need. I fear that
your workaround is currently the best available solution. Please write a
request for enhancement and the owner to [email protected]. I hope that
we can extend the implementation to support your use case.
Regards,
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
