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

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org
           Severity|normal                      |enhancement
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=98
                   |                            |950
           Keywords|                            |needsUXEval

--- Comment #8 from V Stuart Foote <[email protected]> ---
Have watched the video.

The questions and screen capture are:

"Manual page size adjustment by a numeric value is inconvenient
What about an ability to manually drag it like sidebar?
Like this?
Thank you"

Screen capture first shows the Page Style... dialog launched from context menu
and using the Page tab's Paper Format making change(s) to the 'Height:' field.

After showing the above text, it shows the Sidebar deck being dragged wider and
narrower.  And asks question "ability to manually drag it like sidebar".

So, to answer:

Unlike the fielded spinbox as used for a numerical page resize, Mouse or cursor
based drag resize--while feasible--would likely be non-performant.  

The resizable Sidebar deck is a UI element, it has limited impact (i.e. just
viewport adjustments) on the document canvas, so negligible.

On the other hand, resize of a document's page, currently via spin box fields
on the dialog, triggers predictable refresh of the document's layout *only when
Applied* (Apply or OK from the dialog).

UI Drag actions would require dynamic recalculation, perhaps could use a
bounding rectangle to reduce redraw hash.

Of questionable use for the Writer module (even working with tables), while for
the Draw module we already have bug 98950.

IMHO => WF

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to