Description: Configuring a bitmap to show on full page with custom position and size not easy to do/ user friendly Steps to Reproduce: 1. open Writer 2. Format -> Page Style -> Area -> Bitmap 3. Choose A bitmap & tiled mode -> Press apply -> Full page filed 4. Choose custom position & size.. and press apply -> only filled until page border 5. Type width 21 height 29,70. Full page gets filled Actual Results: in Choose custom position & size the width/ height appears to be tile size (1 cm x 1 cm). However if you put 21 height 29,70 a full page will be filled; which is surely confusing Expected Results: 1. Make separate setting for 'full page' or page margins (would also be nice for page color background). If for what ever reason you don't want to border to be included. The old way was 'with borders'. Default maybe full page, but make it optional (which it bitmap area even more useful) 2. This would scale also more logical; scale to page or to page borders. Personally I would prefer percentage default; not seeing the point of doing this in absolutes (as i assume people attempting to fill the p 3. Scale is bit hard to follow. As it has multiple meanings. Scaling an image of 1 x 1 cm to 150 (is increase size). Scale an image of 100x100 for a4 means reducing size. Or scale to margins; scale to page? What is meant here? 4. Add a preview of how it looks on page, it's evilly hard configuring, without seeing what the end result would be. So you go try and error, Apply, edit etc. 5. The position setting doesn't make sense in the case you want to scale to page margins or to page. As it doesn't matter at all. Reproducible: Always User Profile Reset: No Additional Info: Found in 7.1 and in Version: 6.4.0.0.alpha0+ (x64) Build ID: 92d1b0d10ec04f17d116bc54aada652f1c2cac4a CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 164372 [details] Example file Reason for this bug 94826. As what that person did is simply. Pasting an image & setting it to 'background' However attempting to set it background was harder than expected. Or should there be an option like Draw/Impress has?)
We started the new Area fill dialog with a proposal at https://design.blog.documentfoundation.org/2015/12/22/area-fill-options-made-consistent/ that also considered easy to handle bitmaps. However for several reasons it wasn't fully implemented in the GSoC project. Among other because the proposal oversimplified and ignored available options. We have many tickets around this, bug 103223 or bug 113224 are the meta tickets. I suggest to resolve this report as duplicate. It's anyway a bit unspecific.
(In reply to Heiko Tietze from comment #2) > We have many tickets around this, bug 103223 or bug 113224 are the meta > tickets. I suggest to resolve this report as duplicate. It's anyway a bit > unspecific. Telesto: do you agree? If yes, pick a duplicate
(In reply to Buovjaga from comment #3) > (In reply to Heiko Tietze from comment #2) > > We have many tickets around this, bug 103223 or bug 113224 are the meta > > tickets. I suggest to resolve this report as duplicate. It's anyway a bit > > unspecific. > > Telesto: do you agree? If yes, pick a duplicate Not seeing anything similar in those meta bugs (but well only skimmed through)
Telesto, isn't what you want to do simply about changing from "Custom position/size" to "Stretched"?
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp