https://bugs.documentfoundation.org/show_bug.cgi?id=147592

--- Comment #5 from [email protected] <[email protected]> 
---
Correction to my report. 

The statement:
>(...) 
> b) could not replicate in on Windows with inserted Writer documents as OLE 
> objects. (...)

is no longer correct. 

I can replicate it. My confusion was due to the fact that "save" operation
doesn't do anything until there is a change in a document text even tough the
view of document did change and is apparently saved in document. Currently I
can observe, that even with a SINGLE linked view what is seen through linked
view after an update reflects what was visible in inserted document during
recent save.

I may agree that having two views of the same object may be something
developers did not thought about. The fact however that information stored
inside an odt file about a single view looks like:

<draw:object xlink:href="../B.odt" xlink:type="simple" xlink:show="embed"
xlink:actuate="onLoad"/>

shows that there is absolutely no information about what region of document is
to be displayed. This is, I think, conceptually wrong. Sadly I can't see in ODF
specs anything what could suggest a kind of "view port" transformation which
ought to be applied to object, but I am not an expert in it.

I can agree that for <draw:object-ole>, where drawing is fully controlled by an
unknown application this may be a problem, but for well known open document
objects it should be doable.

As it is now there is absolutely no point in using this functionality because
it will only produce a confusion. 

So possibly it is not a programming bug but a conceptual overlook. 

@m.a.riosv

DDE is no-go, because such a document won't be portable open document anymore
(docs do say: "windows only").

I agree that I can get to expected goal in many different ways, but I tried to
do it using that functionality since it looked ideal for the purpose. With it
working as I expected I could have the computing power of Calc with visual
elegance of Writer documents.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to