https://bugs.documentfoundation.org/show_bug.cgi?id=141097
--- Comment #20 from Makrea <agut...@gmail.com> ---
(In reply to Michael Warner from comment #19)
> @Makrea, I am not very familiar with OLE or LO's interaction with it, so
> please forgive if I am asking a bad question. However, in the comment you
> quoted, the words "is active" stood out to me:
>
> // Always veto termination while an OLE object is active
>
> In the use case you provide, it sounds like you don't need to interact with
> OLE any more once the document is open. Is there any way you can de-activate
> or end the OLE session at that point?
Hi Michael Warner,
> please forgive if I am asking a bad question
Feel free to ask all questions.
I'm more than available to see this issue solved once and for all.
> In the use case you provide, it sounds like you don't need to interact with
> OLE any more once the document is open.
That's true most of the times.
I'll give you some real world examples where that's not 100% true.
Say you have a template and you need to insert text and bookmarks.
On this occasion the OLE object that links to the LibreOffice instance will be
used by means of UI and at a lower layer invokes API calls to LibreOffice.
To be more specific say a UI window that you double click to set a specific
bookmark on a template at a specific insertion point.
Say now that the user wants to close and save the template. It can save but
cannot close the template document because of the veto limitation that was
inserted.
I asked on comment 5 what was the use case that needed to be met that caused
this change. All I got was silence....
This is only one example I can give.
Another example is:
Say a Calc sheet and data is exported to cells.
The user can't close the sheet after export.
You will excuse me the sentence but here it goes.
This veto implementation was poorly designed and collides with all real word
use cases that involves user interaction.
>Is there any way you can de-activate
> or end the OLE session at that point?
Maybe. But I feel that isn't a straightforward (point in time) action to be
made because of user unpredictability .
I don't investigated that because my opinion is that this veto exception error
originates from a 100% wrong approach to API LibreOffice usage.
Please see that, as it stands now, it completely disregards the possibility of
real world user interaction with Libreoffice close by UI. Legitimate real world
user actions.
So our course of action was all instances didn't update and this bug link was
made publicly known to all users that updated, reported this issue, and then
had to go back to a previous LibreOffice version.
I think I will give your question back to you.
On comment 13 (3 months ago) I already went somewhat on that course.
>By default the new suggested option can implement this Veto behavior and I
>>will change on my side to permit user interaction to close on GUI.
>If there is already an UNO function regarding this suggestion please send >me
>the link for me to read.
So, is there any way you can de-activate or end the OLE session at that point?
Best regards.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
