Bug 98950

Summary: DRAW: Resize Page by Drag and Drop
Product: LibreOffice Reporter: myh
Component: DrawAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: enhancement CC: buzea.bogdan, heiko.tietze, myh, vsfoote, wzab01
Priority: medium    
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 113354    

Description myh 2016-03-29 08:59:04 UTC
Microsoft Visio supports to use mouse and keyboard to resize the drawing page intuitively: Holding down Ctrl key and moving the mouse cursor to any edge of the page, the mouse cursor icon will change to resize icon. Dragging and dropping the edge by mouse to another position resizes the drawing page.
It is very convenient to reduce redundant white space of a drawing by "drag & drop," and then we can export the drawing to a PDF without cropping the redundant white space by another tool.
Could LibreOffice Draw also support "page resize by drag & drop" in the future?
Comment 1 V Stuart Foote 2016-03-29 14:55:08 UTC
Adding GUI controls is just some of the work that would help controlling the Draw canvas/page.
 
Expect implementing would mean exposing page attributes to GUI manipulation and adding drag handles. 

The Page dialog already offers precise controls of size as well margin--but no "fit to selected" or "fit to objects". And what can't be efficiently done now is to fit the cnavas/page size to the Draw objects (or OLE elements) that are present--removing the default margins.

GUI dragging of handles to resize implies intent to set size to where handles are positioned-- without margins--so basically a crop. So, while implementing the GUI controls providing corresponding "fit to" controls in the page dialog would be helpful.
Comment 2 Robinson Tryon (qubit) 2016-08-25 05:49:44 UTC Comment hidden (obsolete)
Comment 3 Heiko Tietze 2020-02-25 10:16:04 UTC
Removing UX as the request is clear and Stuart's replied comprehensively.
Comment 4 Buovjaga 2021-01-18 17:26:34 UTC
*** Bug 134994 has been marked as a duplicate of this bug. ***