Description: When chopping a really long column into pieces with a fixed width, only the widths of the first view rows are considered. Then you get a warning that the result will spread over already filled cells. Steps to Reproduce: 1. load a document with lots of rows 2. split a column with a big variety of width using "fixed width" 3. try to set the width of the widest cell Actual Results: Step 3 is hardly possible as only the cells you are seeing in the preview are considered in the ruler. The result is the original column is spread over several columns, maybe even overwriting existing cells. You don't have real control over it. Expected Results: The ruler should show the true width of the widest cell. Or there should be a rule that only the columns shown in the ruler are used. Reproducible: Always User Profile Reset: No Additional Info: The true Version is 6.1.5 from Debian Backports (not offered in the list) Workaround: Create a dummy entry in the first line which is for sure longer than the longest cell.
Please attach a sample file, and an image of the import options windows.
Created attachment 148863 [details] test file Try to split entire column B to separate the xxxx from the yyyy. The longer entry in row 109 is not considered in the ruler of the dialog. You could scroll down in the dialog. But imagine a file with ten thousends of lines. This is the simplest example I could imagine.
Created attachment 148864 [details] screenshot In the screenshot you see the narrow ruler of the dialog. It represents the width of the column of the first rows.
(In reply to Nobs Wolf from comment #0) > widths of the first view rows are considered. Then you get a warning that sometimes I doubt on my english ... -> widths of the first FEW rows are considered. Then you get a warning that
Right about the issue to show the wider column without go to it. But for me it's split correctly in two cells.
(In reply to m.a.riosv from comment #5) > Right about the issue to show the wider column without go to it. > > But for me it's split correctly in two cells. I did some more tests: It depends on how you used this feature before. Try using it on a wide column and set some more splits. You can even do that in my example. You can stop when the warning about overwriting existing cells appears. Then start over and split column B in my example. If you scroll down to row 109 you see all the split points you set before. And they will get used even when they are not visible. So maybe the fix could be: Don't use split-points that are not visible in the ruler.
I also suggest to add a button to remove all split points, because previously used split points that are far to the right on the ruler may not be visible if working with shorter text afterwards, and therefore impossible to remove. These additional invisible points sometimes split the text in ways I don't expect, overwriting content of cell to the right of the cell being split.
Dear Nobs Wolf, 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
Still repro in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 722ec600e85cca2e94e82e69f8d13773061172b9 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Dear Nobs Wolf, 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