Created attachment 73641 [details] conditonal formatting created with lo3.5.7 Hi, I have a calendar implemented in lo3 calc. When I open it in lo4, everything looks and works fine. Saving it as ods in lo4 works now, too. However, when I load the file again with lo4, the conditional formatting in the first sheet (Januar) is completely broken because it references the second sheet (Februar). In earlier builds of lo4 every sheet was broken and most of the time it wasn't even possible to save the file due to a "write error". So things have improved, even though not everything is working perfectly right yet. Please find attached the original lo3 spreadsheet and the spreadsheet that results when saving it with lo4. It opens fine in lo3 but not in lo4.
Created attachment 73642 [details] conditional formatting after loading and saving it in lo4 open this file (*-lo4.ods) in lo4 rc2 to see the bug
@Markus: Conditional formatting bug; therefore I add you to CC.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6a82a9908cc5b911dd6783cab69ed3dcb6ba66bb we need to parse the cell address after import, fdo#59843 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Nope, doesn't work yet with http://dev-builds.libreoffice.org/daily/libreoffice-4-0/Linux-x86_64_11-Release-Configuration/2013-01-28_08.35.05/ If I just open the second attachment of this bug I still have weekdays highlighted instead of the weekend. Did you try it and did it work for you? If so, how can I check if your commit is part of the build? The time (8:35) seems to match. In any case, I will try the next build as soon as it becomes available.
A you can see the fix is right now only in master branch for Libreoffice 4.1. So either you grab a daily master build or you have to wait till it has been pushed to the 4-0 and less likely to the 4-0-0 branch.
I see. Where can I find daily master builds? This directory http://dev-builds.libreoffice.org/daily/master/Linux-x86_64_11-Release-Configuration/ is always empty when I look into it. And http://tinderbox.libreoffice.org/MASTER/status.html seems to suggest that AMD64 isn't being built... or looping actually, the current build time is 71556 minutes!? Would be great to have so that I know if a bug I find has already been fixed.
(In reply to comment #6) > I see. Where can I find daily master builds? This directory > > http://dev-builds.libreoffice.org/daily/master/Linux-x86_64_11-Release- > Configuration/ > > is always empty when I look into it. And > http://tinderbox.libreoffice.org/MASTER/status.html seems to suggest that > AMD64 isn't being built... or looping actually, the current build time is > 71556 minutes!? > > Would be great to have so that I know if a bug I find has already been fixed. Most of the tinderboxes are currently building 4.0. But you can use builds from the dbgutil box. While it may crash a few times more often all these crashes should be reported immediately as these additional crashes are assertion failurs in the code.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "libreoffice-4-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=e39fe8bc29af60e849534b6cb1882dbcec363052&h=libreoffice-4-0 we need to parse the cell address after import, fdo#59843 It will be available in LibreOffice 4.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Lovely! Just when I finished downloading the 1GB debug build I noticed your commit. I can confirm that it works now, along with a few other things - all fixed. Thank you.
(In reply to comment #9) > Lovely! Just when I finished downloading the 1GB debug build I noticed your > commit. > > I can confirm that it works now, along with a few other things - all fixed. > Thank you. Hehe :p. Therefore -> VERIFIED FIXED. Thanks Markus!