When creating a double border under a calculation result it views as one single fat border, regardless of border thickness. This single glitch is what keeps me from using libreOffice by now. The problem doesn't appear in OOo
if i add to a cell a double border with very small width then it looks rather like single border, but at 3pt the 2 lines are clearly visible. what exactly are you trying to do that doesn't work?
As stated in bug-cause I'm trying to put two lines under a result. I've tried fiddling with the thickness and the various double border options ... but same result :( For some reason the 'look for updates' only returns an error message and the version is 3.6.3.1 Build ID: f8fce0b I begin to get hint of double-line when up around 3,5-4 pt. but it looks like arse with such thick lines, and that's what's bothering me because it works as one would suspect when in OOo. Same sheet, same everything, but aesthetically as mess in Libre and not so in OOo. I don't get it :(
forgot to mention that the double line effect is visible in the small window where you manage which sides of a cell should have the border pretty much no matter what border configuration I choose .. it's first when applied the problem appears on the actual sheet. Annoying
Created attachment 71978 [details] borders formatted for totals
Created attachment 71980 [details] pdf of borders formatted for totals
confirmed here on 3.6.4 on ubuntu 12.04 64 bit to get the attached results I had to: 1 - Turn off anti-aliasing 2 - Select the cell bottom border as the fourth item up from the bottom in the borders dialogue. yes this is portrayed as a SINGLE line in the dialogue. NONE of the double ones work. Note. Even this border is incorrect since it consist of one correct thin line and a second one below slightly thicker. you can see this both on the print preview by zooming in and also by zooming in on the pdf. This is a regression. See bug 46112 Also see bug 57345 re the anti-alias. I cannot be sure which LO version the bug resurfaced in, since I have been editing old spreadsheets for quite a while rather than creating new ones. This is a total show stopper for any kind of financial work with LibreOffice. (projections, accounts, all our financial records here, annual accounts filed with companies house and charity commission etc) Coincidentally, and very lucky for me (!) I was just about to deploy LO 3.6.4 here to replace our current OOo 3.3 installations when I discovered this bug.
Created attachment 72028 [details] border modified to show correctly
Created attachment 72030 [details] pdf of boder modified to show correctly The anti-alias bug 57345 is a bit of a red herring... The problem is down to errors in the cell border dialogue. Firstly it doesn't respond to change of units properly ie the line type is always shown as a pt size regardless of units chosen for the spreadsheet. But it has always been like this (I think), so still not the answer. Secondly the double borders are assigned line sizes incorrectly. In attachment 71968 [details] the borders are set to: 0.026cm 0.026cm 0.002cm This is in the wrong order. Double Border size should be bottom line first, then spacing, then top line. From the point of view of displaying the things I have found that the spacing needs to be at least .06cm to be able to view at 100% and in preview and printing. See attached 72028 fods file which I have edited and which works ok on my screen with the following settings: 0.002cm 0.06cm 0.002cm Note the corrected order and the slightly overlarge spacing. Also see attached pdf of this correction. I have not been able to find any setting accessible through the borders dialogue which displays correctly. The only way of getting a usable financial spreadsheet from LO is to save it as a .fods and edit it with a text editor! Or, you can save a simple sheet as .fods with say just one cell in it with double border underline. Edit the fods to correct the cell format, then reopen it in calc and copy the cell formatting to new cells as you create them. That's a pretty awful workaround. Think I'd rather go back to OpenOffice 3.3 until this is fixed. Also, I have no way of testing what this looks like when exported as a xls file which is how we have to communicate financially with the outside world.
EDIT: Oh well, I've just exported my corrected file to xls and the double border disappears in all views and scales when reopened in calc (got no windoze here) As an xlsx the bottom border disappears altogether...
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO