https://bugs.documentfoundation.org/show_bug.cgi?id=151762

Heiko Tietze <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|libreoffice-ux-advise@lists |mentoring@documentfoundatio
                   |.freedesktop.org            |n.org
             Blocks|                            |86899, 108519
           Keywords|needsUXEval                 |difficultyInteresting,
                   |                            |easyHack, skillCpp, topicUI
           Severity|normal                      |enhancement
            Summary|Writer : page wrap cant     |Expose Edit and Delete Page
                   |removed if a table starts   |Break as UNO commands
                   |on next page in the first   |
                   |line                        |
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #12 from Heiko Tietze <[email protected]> ---
(In reply to Regina Henschel from comment #10)
> So the user might not even know, that the table
> has a `Text Flow` tab.
Users may also not know that PB is an attribute of the paragraph. You need to
learn complex software.

> `Edit page break` and `Remove page break`... could be made accessible
> from ... the Insert menu next to 'Page break'.
Sounds reasonable, and I suggest to have it under More Breaks. Yet I'm not sure
this would have been a solution for the originally problem.

It could be an interesting easy hack to expose the functions from
sw/source/uibase/docvw/PageBreakWin.cxx as UNO commands with the challenge to
have the state contextually enabled.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=86899
[Bug 86899] [META] Requests for the addition of UNO commands
https://bugs.documentfoundation.org/show_bug.cgi?id=108519
[Bug 108519] [META] Page break bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to