If you try to insert a new OLE object in Writer, you will not be allowed for that object to be a writer document. If you try this in Calc, you will not be allowed to insert a spreadsheet. etc. There is no reason to artificially block the insertion of such objects.
Can not confirm. Using the OLE Insert from File selection, the 'Insert OLE Object' dialog has a radio button 'Create from file' Selection of existing ODF then works into the same LO module. Either "linked" or as a copy. => WFM Version: 25.8.1.1 (X86_64) Build ID: 54047653041915e595ad4e45cccea684809c77b5 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
(In reply to V Stuart Foote from comment #1) > Can not confirm. Using the OLE Insert from File selection, the 'Insert OLE > Object' dialog has a radio button 'Create from file' No, this bug is not about creating from file, it's about creating a _new_ object. I guess I did not phrase the title quite right.
(In reply to Eyal Rozenberg from comment #2) > (In reply to V Stuart Foote from comment #1) > > Can not confirm. Using the OLE Insert from File selection, the 'Insert OLE > > Object' dialog has a radio button 'Create from file' > > No, this bug is not about creating from file, it's about creating a _new_ > object. I guess I did not phrase the title quite right. And that is clearly NOT A BUG! Enhancement for attempting to scope an additional OLE document object of the same type from within current LO document module is nonsensical. There is no work flow requiring such. And even if, how would current LO module manage it as a discrete ODF document? Believe it would require extending ODF to hold OLE of like ODF format. Working with a fully instantiated ODF document as OLE (the 'Create from file' handling) is well established, and is what folks understand as functional. OLE of ODF document types other than current module are routine, e.g. Chart, Table, Formula.
(In reply to V Stuart Foote from comment #3) > And that is clearly NOT A BUG! Of course it's a bug - as you've just illustrated by pointing out that we can introduce a same-module OLE-object document - as long as we begin with a file on disk rather than starting from scratch. > There is no work flow requiring such. Same workflow as for any OLE object. > And even if, how would current LO module manage it as a discrete ODF > document? What do you mean, how? It already does that. It's just that the list in the dialog is missing an item. > Believe it would require extending ODF to hold OLE of like ODF > format. All it needs is not to filter an item from the list of kinds of ODF documents, that's all.