https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Mike Kaganski changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #23 from Mike Kaganski ---
(In reply to pierre-yves samyn from comment #22)
Ref: bug 140702.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #22 from pierre-yves samyn ---
Hi Mike, others
(In reply to Mike Kaganski from comment #12)
> If you need something that can move, you need to anchor that to something
> that is movable. That is content. You have plenty of
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Mike Kaganski changed:
What|Removed |Added
CC||jack.de...@cantab.net
---
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #20 from Mike Kaganski ---
(In reply to Stanislav Horacek from comment #17)
> However, when such an image (anchored to the paragraph and with position
> relative to the page) is moved manually, then the position is changed to
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #19 from Mike Kaganski ---
(In reply to Stanislav Horacek from comment #17)
> (I think that the most intuitive mental model is "fixing image within the
> page -> anchor it to the page" and "moving image with the paragraph ->
>
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #18 from Mike Kaganski ---
(In reply to Stanislav Horacek from comment #17)
> However, when such an image (anchored to the paragraph and with position
> relative to the page) is moved manually, then the position is changed to
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #17 from Stanislav Horacek ---
OK, I see your point - thanks for that!
I admit I've never considered that anchoring to a floating paragraph/character
could actually mean fixing the position within the page. (I think that the
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #16 from Mike Kaganski ---
(In reply to Stanislav Horacek from comment #15)
Please look at comment 14. It is exactly the case of user error, using wrong
feature, not knowing what to use correctly.
I even wrote:
> I believe
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #15 from Stanislav Horacek ---
I don't agree with this too developer-centric approach. From user's point of
view, this requirement is valid: I want to anchor an object such a way that it
moves together with some page content
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #14 from Mike Kaganski ---
FTR: https://wiki.documentfoundation.org/Faq/Writer/AnchoringAndPositioning may
be helpful to allow users to choose the correct anchoring and positioning. I
believe that using wrong "to page"
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Buovjaga changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #12 from Mike Kaganski ---
How is this "NEW"? Does *anybody* here who imagine "this" would be "a very
useful enhancement" realize what "this" might be? How could something be
anchored to something that does not exist? There
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #11 from R. Green ---
There are several common triggers which can cause page-anchored images to slip
out of position: adjusting line or paragraph spacing, changing page dimensions
etc. So, IMV, this would be a very useful
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #10 from Mike Kaganski ---
1. There's no "to page" anchor in Word.
2. Anchor "to page" is "to specific physical page number", and it should not
move to another physical page number. If an object should move with some
neighbour
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Samuel Mehrbrodt (CIB) changed:
What|Removed |Added
CC||bram.way...@utexas.edu
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #8 from Buovjaga ---
(In reply to Jose from comment #7)
> Is there a way to crow funding this option? I mean, I really want this to be
> implemented and for sure many other people will want. How can we 'sponsor'
> this
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Jose changed:
What|Removed |Added
Hardware|x86-64 (AMD64) |All
OS|Windows (All)
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #7 from Jose ---
(In reply to RGB from comment #5)
> [Copying a comment from Bug 117329]
>
> --
>
> Just to make things clear, a quick and oversimplified review of what LaTeX
> does by default (users can change those
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Buovjaga changed:
What|Removed |Added
CC||tele...@surfxs.nl
--- Comment #6 from
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
RGB changed:
What|Removed |Added
CC||rgb.m...@gmail.com
--- Comment #5 from RGB
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Heiko Tietze changed:
What|Removed |Added
CC||joruru201...@hotmail.com
---
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
--- Comment #3 from Stefan ---
Hello Cor Nouws,
locking something to paragraphs is good for many things, and I use it daily, of
course.
But for certain types of manuals and instruction sheets I prefer locking object
to the page, as
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Cor Nouws changed:
What|Removed |Added
CC||c...@nouenoff.nl
--- Comment #2 from
https://bugs.documentfoundation.org/show_bug.cgi?id=89477
Dieter Praas changed:
What|Removed |Added
See Also||https://bugs.documentfounda
25 matches
Mail list logo