Steps to reproduce: Open Calc with a new document. Format two colums with format "[HH]:MM". This format interprets numbers as hours, where 1 corresponds to "24:00", 2 gives "48:00" and so on. Enter some data. Create a XY diagram that displays these data. Try to format the Y axis of the diagram: Uncheck all automatic scaling options. Set the "main interval" (?) (German: "Hauptintervall") to some value other than "24:00:00" (i.e. the value given by the automatic setting). Click "OK" to save the settings. The Y axis of the diagram shows the marks as specified. Open the dialog box to format the Y axis again. Current behavior: The dialog box shows "24:00:00" as main increment, clicking "OK" changes the settings of the Y axis accordingly. Formatting the X axis shows the same problem. Expected behavior: The main increment should show the same value as before, and clicking "OK" without doing any changes should not change the diagram. Platform: LibreOffice 4.2.4.2 german, Windows 7
He! I had to deal exactly with the same behaviour an hour ago! Markings as NEW.
Created attachment 99570 [details] Sample document Sample document. * Double click on the chart to select it. * Format > Axis > X axis (or Y) * In tab 'Scale' uncheck 'automatic' for the 'Major interval' * Enter '00:10:00' as value for the Major interval * OK Behavior: major interval changes to 00:10:00, which is good. Although, if you go back to the same dialog -> Major interval is changed to 24:00:00 If you now change something else, and don't notice this and hit OK -> major interval will be 24:00:00 Summary: major interval is resetted all the time Kind regards, Joren
Katarina Behrens committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b8979cae28cc541a1cfca1b4d2f79b92308bcda0 fdo#79028: ungroup widgets and Show() them correctly 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.
Hi Katarina, Tested using Mac OSX 10.9 with LibreOffice Version: 4.4.0.0.alpha0+ Build ID: b8979cae28cc541a1cfca1b4d2f79b92308bcda0 TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-06-13_22:10:11 Looks fixed! Thanks! Can you please backport the fix to 4.3 and 4.2 branches as well :-)? Kind regards, Joren
> Can you please backport the fix to 4.3 and 4.2 branches as well :-)? I most certainly can, but first need to ask someone how to do that (via gerrit, I presume) -- I have never backported anything so far, eheh
(In reply to comment #5) > > Can you please backport the fix to 4.3 and 4.2 branches as well :-)? > > I most certainly can, but first need to ask someone how to do that (via > gerrit, I presume) -- I have never backported anything so far, eheh Mmh, it's already been a while I did that for the last time :-). I think you have to checkout to your local branch where you did your changes. Then do 'git commit -a' and don't change anything to the name or commit ID etc. Then 'git push origin <localBranchName>:refs/for/libreoffice-4-3'. Same for 4-2. But you can always ask other devs at IRC of course ;-). Thanks for fixing! Kind regards, Joren
Katarina Behrens committed a patch related to this issue. It has been pushed to "libreoffice-4-3": http://cgit.freedesktop.org/libreoffice/core/commit/?id=0ea3f764d70b9223a733d8c2857f42fefd17c536&h=libreoffice-4-3 fdo#79028: ungroup widgets and Show() them correctly It will be available in LibreOffice 4.3. 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.
*** Bug 80458 has been marked as a duplicate of this bug. ***
*** Bug 78261 has been marked as a duplicate of this bug. ***
*** Bug 84632 has been marked as a duplicate of this bug. ***