[Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 V Stuart Foote changed: What|Removed |Added CC||par...@narod.ru --- Comment #38 from V Stuart Foote --- *** Bug 161175 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 V Stuart Foote changed: What|Removed |Added CC||kira.t...@gmail.com --- Comment #37 from V Stuart Foote --- *** Bug 160815 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #36 from Mike Kaganski --- (In reply to Arnold Couchard from comment #35) Then please continue using this feature as before, just using the dialog and/or customized toolbar/menu. It is not going to be removed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #35 from Arnold Couchard --- "anchor to page" was a very important option for us. We anre publishers and consultant in publishing and in all books, you have a pagenumber in the top or the bottom of pages. But, whithout "anchor to page" option, it is no more possible for us to mask some page numbers. We do it using a single form which is anchored on the page et just transfered by copy to all the pages where it's needed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #34 from Alex Thurgood --- Not that it will change anything, but just to add my ha'penneths worth to the disgruntled user base whom this change affects. I use this "power" feature every time I type a letter with my scanned signature inserted into it. I deliberately anchor the image to the page, and have done now for over 20 years of using StarOffice/OpenOffice/LibreOffice. This page constitutes my signature page, and is preceded by a page break. If I use an existing document to overwrite and/or modify its content, then having the signature remain on the allocated last page is a useful check to make sure I haven't left anything I don't want by mistake. As a result, for all of this feature being deemed a "power user" feature, the change has broken my longstanding workflow. On both a personal and professional level, I don't find that at all helpful, nor do I find the recommendation by some here to "simply" reconfigure the submenu with the appropriate UNO command to be appropriate either. The fact is that user configuration changes to menus/submenus have had a tendency in my experience in the past to get overwritten by newer versions of the software. What that means is that I've gone from a simplistic workflow to a now much more complicated process of having to reconfigure the menu, and hope that my change doesn't somehow get overwritten with a future version update, and/or save my application configuration somewhere else. Please would someone explain to me how that has simplified my life ? By all means, encourage users to use the software in a way which is deemed "the one true way", but please don't remove stuff that people have relied upon for 20+ years and then tell them that they only have to "simply" reconfigure their environment to bring it back. That kind of approach doesn't endear users like myself to the product. It is literally another straw on the camel's back. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Mike Kaganski changed: What|Removed |Added CC||polygrap...@gmail.com --- Comment #33 from Mike Kaganski --- *** Bug 148436 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Mike Kaganski changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #32 from Mike Kaganski --- So the change was intended (and the original report, which has identified the change from the start, and knew that it was intended, claimed "regression" incorrectly); its reasons are sound; everyone who really needs the function is able to use it from the respective dialog; it may be also added to menus using normal customization methods. It is a power user; and no power user would be unable to find it. When poser users ignore the facts and just claim something crap because of own arrogance, that is not an argument. Closing WONTFIX. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #31 from Werner Schneider --- Not all users use L.O. for the same applications. For our applications, the anchor on the side in the context menu is missing. This is crap! Basta! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #30 from Mike Kaganski --- (In reply to Werner Schneider from comment #29) > So what is this? So far, everyone has been able to choose how they want to > anchor in the context menu No. "I have been able to choose how I want to anchor" is *not* the same as "everyone". That you know how anchoring and positioning works is good, but that doesn't mean that everybody does; and careful reading of the issue would allow you to discover that the rationale is *multiple* issues in users who are confused by the feature. Anchoring to page is not intuitive to users; it has its serious drawbacks that should be realized when it is used; and so it is a *power user* feature, that should not be offered as prominently, to avoid more confusion in inexperienced users than it brings advantage to those who would be able to find it anyway. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #29 from Werner Schneider --- Thank you for the hints! I already know them. They all have their place, just like the anchor on the side. After all, it has been used successfully for many years. There was no advantage in removing it from the context menu, only disadvantages. So what is this? So far, everyone has been able to choose how they want to anchor in the context menu, and that was a good thing. Why is something like this being changed, it makes no sense. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #28 from Regina Henschel --- (In reply to Werner Schneider from comment #26) > If you use an paragraph and protect the position of the inserted objects, > then the objects will move if you insert something before the paragraph, > because the protection is only effective inside the paragraph. That's why > anchoring to the side is important. > I think I can judge what I need and what not. Hopefully more proven features > won't be cut. Assume you have anchored an object "to page" and this page is currently the fifth page of the document. When you then enter a TOC on one page and a preface on one page at the beginning, then the object is still on the fifth page of the document. But this fifth page is two pages before the content, where the object was when you had anchored the object. That is very likely not the behavior you want. To keep the object at top of page, for example, you anchor it to paragraph. Then in the Properties or the Position&Size dialog (depends on object), tab Type go to the section Position. There you set Horizontal... To and Vertical... To to 'Entire Page' or 'Page text area' as needed. When you then enter pages before the anchor paragraph, then this paragraph might go to the next page and the objects too. But the objects are still at the same position relative to the page as before. You only need to know, that you must not move the object by mouse or keyboard, because that turns the absolute position back to position relative to paragraph. If you insist on using "to page" then add the command to a toolbar or context menu respectively, see comment #20. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #27 from Telesto --- (In reply to Werner Schneider from comment #26) Only a suggestion: Tools -> Customize -> Context Menu Tab (or Toolbars tab) 1) Target -> Image (or for toolbars tab 'Frame') 2) Search for 'To Page' 3) Select Anchor To Page 4. Arrow right button in 5. Move it the desired position in context menu Press OK. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #26 from Werner Schneider --- I know the function on the side in the properties, I also use it as a workaround because it is now missing in the context menu. If you use an paragraph and protect the position of the inserted objects, then the objects will move if you insert something before the paragraph, because the protection is only effective inside the paragraph. That's why anchoring to the side is important. I think I can judge what I need and what not. Hopefully more proven features won't be cut. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #25 from Mike Kaganski --- (In reply to Werner Schneider from comment #24) > You can no longer create layouts that actually remain fixed. Yes you can: the "to page" anchoring is there in the object properties dialog. But are you sure that you really need that anchoring? Most of the time, people believe they need that, when in fact they need "to paragraph" anchoring, and some fixed *positioning* (as explained in FAQ linked in comment 12). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 --- Comment #24 from Werner Schneider --- I do not understand that. As it is now, it is misleading and incomprehensible! You can no longer create layouts that actually remain fixed. This definitely needs to be changed! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Buovjaga changed: What|Removed |Added CC||bor...@t-online.de --- Comment #23 from Buovjaga --- *** Bug 146816 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Mike Kaganski changed: What|Removed |Added CC||r.lehme...@freenet.de --- Comment #22 from Mike Kaganski --- *** Bug 146374 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists | |.freedesktop.org| Keywords|needsUXEval | --- Comment #21 from Heiko Tietze --- No need for further input from UX. The patch was initiated by the group and I see no argument challenging the reason: safety/consistency. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 V Stuart Foote changed: What|Removed |Added Keywords|regression |needsUXEval Ever confirmed|1 |0 Summary|It disappeared "To page"|Removal of "To page" |item from Anchor drop-down |anchor context menu entries |widget on Frame toolbar in |for frames, images, OLE |Writer |objects (comment 3) Status|NEW |UNCONFIRMED CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #20 from V Stuart Foote --- Removal from the Anchor context menus and TB split button was a little heavy handed, but NAB. Users needing a 'to Page' anchor (e.g. for laying out a large single page poster) can customize and add the 'Anchor to Page' (.uno:SetAnchorToPage) to a specific context menu object type--or to a generic Menu, Toolbar, NB, or a Keyboard shortcut assignment. Back to UX-Advise IMHO a => WF is fair. Not too much to be gained by reverting, but some Help and UG treatment is certainly now needed. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
