https://bugs.documentfoundation.org/show_bug.cgi?id=149376
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |2011 --- Comment #11 from Justin L <[email protected]> --- Regina notes in duplicate bug 57599 that the "allow overlap" checkbox first appeared in LO 6.4 thanks to vmiklos' work for bug 124600. I really like duplicate bug 142964's described use case - drag and drop. Definitely I would not expect the images to be stacked on top of each other in that case (and I agree with the general idea of avoiding image overlap as a default). bug 102011 might be useful parallel. That leads to sw/source/core/doc/DocumentStylePoolManager.cxx SwFormatWrapInfluenceOnObjPos aOverlap(; aOverlap.SetAllowOverlap(false); aSet.Put(aOverlap); I'm not noticing the concern that this might affect previous documents. In fact, when I import an existing document, the graphics style itself still defaults to "overlap" as before. Doing this has the side effect of also creating draw:wrap-influence-on-position="once-concurrent" since this one format-setting handles multiple properties. P.S. Even with that change, Drag and Drop still didn't produce non-overlapping images, even though each image now specifies no-overlap (at least the ones I was testing with). It kind-of worked if a single page was large enough to hold them all. -- You are receiving this mail because: You are the assignee for the bug.
