Description: https://drive.google.com/file/d/1FFgQru-jEAoADyvNKMl3kvfcbokWCjie/view?usp=sharing Steps to Reproduce: 1.Drag a page by its borders to change its size 2. 3. Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: No Additional Info: .
1. Do not create bugs like "description: see an external link with a v1deo, so that (1) you can't read it until you watch something long, and (2) the bug report may become useless as soon as I or my hoster decides to remove the video"; 2. What is the use case? You create pages to match some media. If you use standard paper, you have a choice. If you have a non-standard paper, you still have its hard dimensions. Even if your media is e.g. screen, it's not something free-sized. A case when your page should be mouse-adjusted is unclear.
(In reply to Mike Kaganski from comment #1) > 1. Do not create bugs like "description: see an external link with a v1deo, > so that (1) you can't read it until you watch something long, and (2) the > bug report may become useless as soon as I or my hoster decides to remove > the video"; > > 2. What is the use case? You create pages to match some media. If you use > standard paper, you have a choice. If you have a non-standard paper, you > still have its hard dimensions. Even if your media is e.g. screen, it's not > something free-sized. A case when your page should be mouse-adjusted is > unclear. I don't mean offence, but you don't sound too encouraging when it comes to sharing suggestions and sentiments No one will be able to express anything if they are forced to abide by cosmetic formalities that few people care about
(In reply to Mike Kaganski from comment #1) > 1. Do not create bugs like "description: see an external link with a v1deo, > so that (1) you can't read it until you watch something long, and (2) the > bug report may become useless as soon as I or my hoster decides to remove > the video"; > > 2. What is the use case? You create pages to match some media. If you use > standard paper, you have a choice. If you have a non-standard paper, you > still have its hard dimensions. Even if your media is e.g. screen, it's not > something free-sized. A case when your page should be mouse-adjusted is > unclear. That's Google Drive, I believe nothing will happen. It's been working for more than a decade
(In reply to Danat from comment #2) > I don't mean offence, but you don't sound too encouraging when it comes to > sharing suggestions and sentiments > > No one will be able to express anything if they are forced to abide by > cosmetic formalities that few people care about Thousands suggestions come in a proper shape - so definitely *someone* is able and willing to do things properly. "formalities that few people care about" is a direct offence. You are someone suggesting something. Well, thank you for having interest ... but it's you who wants something. You expect people unknown to you, to spend their *free time* (they are mostly volunteers!) see and understand what you try to tell them. If *you* don't care about things that help volunteers here (spending much time, devoting their life resources to improve it) to do it comfortably - I have no wish to review and help you moving your suggestions forward. (In reply to Danat from comment #3) > That's Google Drive, I believe nothing will happen. It's been working for > more than a decade I don't care what you believe about external resources. You have no way of telling what happens tomorrow, both with that resource, and with ability of a particular person reading the bug here to access that resource.
(In reply to Mike Kaganski from comment #4) > (In reply to Danat from comment #2) > > I don't mean offence, but you don't sound too encouraging when it comes to > > sharing suggestions and sentiments > > > > No one will be able to express anything if they are forced to abide by > > cosmetic formalities that few people care about > > Thousands suggestions come in a proper shape - so definitely *someone* is > able and willing to do things properly. > > "formalities that few people care about" is a direct offence. You are > someone suggesting something. Well, thank you for having interest ... but > it's you who wants something. You expect people unknown to you, to spend > their *free time* (they are mostly volunteers!) see and understand what you > try to tell them. If *you* don't care about things that help volunteers here > (spending much time, devoting their life resources to improve it) to do it > comfortably - I have no wish to review and help you moving your suggestions > forward. > > (In reply to Danat from comment #3) > > That's Google Drive, I believe nothing will happen. It's been working for > > more than a decade > > I don't care what you believe about external resources. You have no way of > telling what happens tomorrow, both with that resource, and with ability of > a particular person reading the bug here to access that resource. If something unexpected happens - we can work it out. I have all the videos on my computer, I will be able to retrieve them, and I remember everything. You can just ask me That's actually out of respect that I share videos. Because I want people to not have any confusion about my concerns. If I explained things by words, even despite best efforts, it wouldn't be easy to understand for anyone I come from a different background, and I'm not skilled at explaining software bugs with spoken language, so have understanding. But I try to learn and get better
Created attachment 203594 [details] tdf169126 adjusting page size for existing document (In reply to Danat from comment #5) > If something unexpected happens - we can work it out. I have all the videos > on my computer, I will be able to retrieve them, and I remember everything. > You can just ask me > > That's actually out of respect that I share videos. Because I want people to > not have any confusion about my concerns. If I explained things by words, > even despite best efforts, it wouldn't be easy to understand for anyone > > I come from a different background, and I'm not skilled at explaining > software bugs with spoken language, so have understanding. But I try to > learn and get better Understood, simply create the BZ issue with use case and description and THEN attach your supporting content, e.g. a video, or a test document, or ... Though compressing the screen capture to reduce its size is helpful. Sending us off to some external sharing service is not appreciated, where often there are access issues and potentially legitimate security concerns. Meanwhile, I've attached your video to this BZ instance.
(In reply to V Stuart Foote from comment #6) > Created attachment 203594 [details] > tdf169126 adjusting page size for existing document > > (In reply to Danat from comment #5) > > > If something unexpected happens - we can work it out. I have all the videos > > on my computer, I will be able to retrieve them, and I remember everything. > > You can just ask me > > > > That's actually out of respect that I share videos. Because I want people to > > not have any confusion about my concerns. If I explained things by words, > > even despite best efforts, it wouldn't be easy to understand for anyone > > > > I come from a different background, and I'm not skilled at explaining > > software bugs with spoken language, so have understanding. But I try to > > learn and get better > > Understood, simply create the BZ issue with use case and description and > THEN attach your supporting content, e.g. a video, or a test document, or ... > > Though compressing the screen capture to reduce its size is helpful. > > Sending us off to some external sharing service is not appreciated, where > often there are access issues and potentially legitimate security concerns. > > Meanwhile, I've attached your video to this BZ instance. Yes, that's one of my concerns that videos are crisp and not blurry. It takes effort to watch a video, and it is not my desire to make it worse by handing out low quality videos But I will try to attach videos in here as well Thank you
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
(In reply to V Stuart Foote from comment #8) > 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 This whole thing isn't very serious, but I thought that such a thing - if properly implemented - would make LibreOffice standout. Is there any office app that has it? Though I can imagine that users would be accidentally dragging the pages often Maybe there could be an algorithm like right-click->resize page->it lets you resize it->manually drag the page->it doesn't let you drag anymore until you repeat that algorithm But maybe that's not necessary and just let them drag without any prior steps Or maybe you could add a setting like "allow manual resizing of pages by dragging", and that sounds like the most ideal path to me
(In reply to V Stuart Foote from comment #8) > Of questionable use for the Writer module (even working with tables), while > for the Draw module we already have bug 98950. So obviously a duplicate. I'm not convinced by the use case. What's wrong with a proper page size rather than some random value? A use case might be "I want to change the page size from A4 to A5 but don't know the exact values. However I know it's the next smaller paper.", or the like. Would be wrong, of course, just an example. Up for discussion on the other bug. (In reply to Danat from comment #9) > Is there any office app that has it? That's a good question. Perhaps for good reasons. *** This bug has been marked as a duplicate of bug 98950 ***