https://bugs.documentfoundation.org/show_bug.cgi?id=139057
--- Comment #10 from Michael Stahl (allotropia) <michael.st...@allotropia.de> --- (In reply to Telesto from comment #9) > Created attachment 180761 [details] > Example file Second attempt > > (In reply to Michael Stahl (allotropia) from comment #8) > > i don't think there's an easy tweak to this that preserves the API > > compatibility that comment#4 is about, and it's a rather minor problem, you > > can always click on the image to delete it that way. > > A small retry probably better describing the 'issue'. Primary question: > What's the value of anchoring an image to an character if the anchor is > broken with ease. The anchor suggests a connection between 'the character' > and the image . The image is positioned relative to the anchor point, so if > the characters move (drag/drop or copy/paste) the image should be following. > > 1. Open the attached file > 2. Double click Lorem Ipsum > 3. Drag the text to the top of the page (say it's a list without bullets) wow, writer can do that? > 4. Notice the image moving (why: image is anchored to character, and the > anchor is manually attached to 'm' of ipsum the anchor is between "u" and "m" so it is not at the end of the paragraph so it is included in the selection. > 5. CTRL+Z > 6. Change the anchor of the image to 'to paragraph' > 7. Change the anchor back to 'to character' (anchor will but after ipsum). > Now drag the text up again.. Image stay's behind (expected to move along > with the text) as in 4 now the anchor is after "m" at the end of the paragraph so it is not included in the selection. > 8. Undo the dragging up (but anchor still behind 'ipsum') > 9. Press CTRL+A and enable bulleted list > 10. Move Ipsum Lorum up (with arrows). Notice the anchor moving along. now this moves entire nodes, so anything attached to the node will move with it (except things that span multiple nodes, then it gets complicated and maybe crash prone...). > I guess there being an explanation for each and every case in technical > sense. But from end-user perspective this kind of arbitrary. > > And well 'to character' has to states. (A). Truly positioned to a character. > (B) put after a characters (most common, I guess). Which is not truly a to > character anchor, IMHO generally anything in writer is either a character itself or positioned *between* 2 characters; "as-char" is an example of the former, "at-char" an example of the latter, and "at-para"/"at-fly"/"at-page" are weird exceptions. -- You are receiving this mail because: You are the assignee for the bug.
