Created attachment 46279 [details] Sample document Number of Decimal point can't save in [Major Interval]textbox. I tested package LibO_3.4.0beta3_Win_x86_install_multi.exe on WindowsXP. How to reproduce the problem. 1.Open attached "SampleChart.ods" 2.Graph area double click and right click on Y axis 3.[Format Axis] click on contextmenu 4.[Scale]tab click 5.[Automatic]checkbox uncheck and input "0.5" in textbox on [Major interval]Item 6.[OK]click 7.[Format Axis] click on context menu on Y Axis 8.[Major interval] value should be keep "0.5" but that has changed "1" unexpectedly.
Reproduced this behavior with the master branch built on my Debian box.
One for kohei? @Abe-san, please do re-assign it to yourself, if you would like to work on it. Thank you!
Created attachment 46404 [details] a proposed fix OK, let me propose a fix as attached. @Kohei, please give it your careful eyes.
(In reply to comment #3) > Created an attachment (id=46404) [details] > a proposed fix > > OK, let me propose a fix as attached. > > @Kohei, please give it your careful eyes. Well, the patch does fix this, but I don't know if it's the right place to put a fix in. The problem is that, the date control is hidden, yet its IsVisible() method returns true, which to me is wrong, since that control was never visible to begin with. Someone may have changes the visibility handling in the vcl code, which accidentally changes the behavior over here in the chart2 code...
Ok. I figured it out. The logic there depends on the date control being invisible when the axis date type is not date. The problem comes when that code path is reached *before* the it has the chance to set its real visibility of "false", so it depends on the initial visibility of that control which happens to be "true". When you switch to another tab page, and come back to the Scale page, everything works correctly because it now has the correct visibility. The solution I like best is to explicitly set the visibility of all the dynamic controls to "false" when that tab page class is constructed, then everything works as expected.
http://cgit.freedesktop.org/libreoffice/calc/commit/?h=libreoffice-3-4&id=3f39523ac9284c55c0e9c380750bd5dce213ed19 Fixed in 3.4.
Thanks a lot for your quick response! (In reply to comment #5) > The logic there depends on the date control being invisible when the axis date > type is not date. The problem comes when that code path is reached *before* > the it has the chance to set its real visibility of "false", so it depends on > the initial visibility of that control which happens to be "true". Anyway I'm not yet sure why&how the initial visibility of that control which happens to be "true"...