I try to attach my X-axis to start or end of Y-axis. It attaches, but does not save in xls file format. So I can see the result, I can save file, but, when I will reopen it, it looks like before change.
@Ilya : sorry, I don't understand what you are trying to do. pLease provide a sample document with detailed instructions on how to reproduce the problem. Please also indicate which version of LibreOffice you are using : AppStore or download from TDF servers ?
Created attachment 118787 [details] File to reproduce the problem
Hope that this will help: LibreOffice -> File -> Calc Spreadsheet In cells enter any two points as X-Y coords (4 values, 2 for each coord) Insert -> Chart -> XY (Scatter) , select points to create a plot Now you will see, that X axis is attached to some automatically selected point on Y axis. If you will select X-axis -> [right-mouse-button click] -> Format axis -> Positioning -> Axis Line -> Cross other axis at - select smth other to see ypur X axis moved. Save file to xls file. Reopen. I always get X axis at initial position on Y axis.
Created attachment 118790 [details] Set to 2 I cannot reproduce this bug with Version: 5.1.0.0.alpha1+ Build ID: afce2eee1d163d942385c7b33db4901b3c71135d Format axis -> Positioning -> Axis Line -> Cross other axis at -> 2 Save as XLS Close Open -> X crosses at 2
My version is 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Yes, if I will set a value, then it will be fine. But try to select "Start" or "End". It will reattach to the lower end of axis after reopening.
Confirming on Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale : fr-FR (fr.UTF-8)
Confirming also in Version: 5.1.0.0.alpha1+ Build ID: af433b6fff17e4e835043797063061055643b614 Locale : fr-FR (fr.UTF-8) OSX 10.10.5
There are a couple of issues here. First of all Excel does not have an exact 1-to-1 match for Axis crosses at "Start" and "End". Instead Excel has "Automatic" and "Maximum Axis Value". End seems to match closely to "Maximum Axis Value". However Start does not. For example when I created a scatter chart in Calc, set to start, exported it to XLSX, and opened it in Excel, Excel correctly displayed the chart with axis crosses at "Automatic" AND a value of -1.5(this is greyed out). When I saved as XLS, Excel gave the following warning: "This file contained features which were not recognized by this version of Excel. These features will not be saved. The resulting chart crossed at 0, not 1.5 when opened in Excel. Exactly like Calc does when it exports this chart. The difference is Excel sets it to automatic while calc sets it to 0. But the end result is the same. The good news is End appears to be the same as "Maximum Axis Value" and the binary format does support both "Automatic" and "Maximum Axis Value". The exporter should be using these parameters instead of 0. I'll attach examples to be analyzed with a tool like oledump. Ilya, For future reference, below is what you should have included in your original Description along with a sample document. This is how to write a good bug report. The steps to reproduce are: 1. Create a XY (Scatter) 2. Edit the chart 3. Format axis -> Positioning -> Axis Line -> Cross other axis at -> Select Start or Finish 4. Save as XLS 5. Close and reopen Expected results: Axis remains at start or finish Actual results: Axis set to value=0
Created attachment 118814 [details] XLS scatter chart set to "Maximum Axis Value" saved by Excel
Created attachment 118815 [details] XLS scatter chart set to Automatic(Start?) saved by Excel
One more data point. The importer converts "Maximum Axis Value" to "End", while it converts "Automatic" to Value = 0. So our exporter should covert "End" to "Maximum Axis Value", but we should convert start to a Value=.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Created attachment 130129 [details] Native ODS. To Reproduce Save As .xls Still not exporting correctly in Version: 5.4.0.0.alpha0+ (x64) Build ID: bf80bbb7b75febc2769d6b64e6981224982f8fe2
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still not exporting correctly in Version: 6.1.0.0.alpha0+ (x64) Build ID: adff6293ce22d84e5a380aa649e7d0f0ffdc4d80
Still not exporting correctly in Version: 6.3.0.0.alpha0+ Build ID: 45f4de6d333aa3fa5873cf8e1146286c74960557
Dear Ilya, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Ilya, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug