Description: Rotated Text in Cell not shown (invisible) if angel is not 0,90,180,270 deg. Example 98 deg. I have isolates the content.xml with one text in A1 where it is ok, and an other Cell where it is not ok. Looks like a incompatibility between 5.x and 6.x LO. Steps to Reproduce: 1. WITH LO 5.3.5.2 Place some random Text. Do not take A1 take a place like B3. 2. rotate it by e.g. 82 deg. 3. looks fine, even if scrolling... Save it please. 4. Open the File wit an LO 6.0.X.X. The cell wil be shown a very short time an then stay invisible, if you rotatet it to 90 deg. it is fine. 5. Take already rotated cell from an ods-file which is build by a LO 5.2.x.x version by Copy & Paste then you get this issue too. Actual Results: invisible Text Expected Results: visible, rotatet text in cell Reproducible: Sometimes User Profile Reset: No Additional Info: Sometimes srcolling out of screen and back or resizing the cell shows text for less a second. Look like a kind of repainting error. Testet on Win 10 and Win 7 Test on LO 6.0.0.3 and 6.0.1.1 failed Test on LO 5.3.5.2 is ok Here is a part of the content.xml where i presume the issue (locate for rotation in this snippet) : <style:style style:name="ce2" style:family="table-cell" style:parent-style-name="Default"> <style:table-cell-properties style:rotation-angle="79"/> </style:style> <style:style style:name="ce1" style:family="table-cell" style:parent-style-name="Überschrift_20_1" style:data-style-name="N0"> <style:table-cell-properties style:glyph-orientation-vertical="0" style:cell-protect="protected" style:print-content="true" style:text-align-source="fix" style:repeat-content="false" fo:background-color="transparent" fo:wrap-option="wrap" fo:border="none" style:direction="ltr" style:rotation-angle="82" style:rotation-align="none" style:shrink-to-fit="false" style:vertical-align="middle" loext:vertical-justify="auto"/> <style:paragraph-properties fo:text-align="center" css3t:text-justify="auto" fo:margin-left="0mm" style:writing-mode="page"/> <style:text-properties style:use-window-font-color="true" style:text-outline="false" style:text-line-through-style="none" style:text-line-through-type="none" style:font-name="Arial" fo:font-size="10pt" fo:font-style="normal" fo:text-shadow="none" style:text-underline-style="none" fo:font-weight="bold" style:font-size-asian="10pt" style:font-style-asian="normal" style:font-weight-asian="bold" style:font-size-complex="10pt" style:font-style-complex="normal" style:font-weight-complex="bold"/> </style:style> </office:automatic-styles> OpenGL does not matter. User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Created attachment 139731 [details] Example for Issue Rotatet Text gets invisble
f71251dce8a2c3f2cf8506555ecb2f5f5a715fc4 is the first bad commit commit f71251dce8a2c3f2cf8506555ecb2f5f5a715fc4 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sun Jul 30 23:57:30 2017 -0700 source c394363c84064c041391627602665ea1fa74db60 source c394363c84064c041391627602665ea1fa74db60 source c9253818ec8252169c20450b41878be459568d95 source 242a796a71e29a1d8cdc4dd71d2465b898db32ab source 6d327ffeb12134e28b975b1894b03870fcddf31d source b6076ea5ce60bc1c971db502af3c963da51d8f82 source ce1b56ae4ad35fbb5e2f5cc6f4b7ce4839f4e285 source 20ecb4b7b807b63d25195c44c02cb5bf0624ab7a source 0163984ce76141665296969118791a9ffbf076eb source b1fd54a408602126003ffd5032fb86e95b2744cb source 569ae950f728c658be559d44932a0622df3ed268 source 0160766097798806ce89533b25124477b1a2996a source 875ec879c098f39bc4ed552d31f28e8e67942804 source 2b1d6f0d3b0b025148c81986ba7f109659d838af source aba73077851a744c06e72b3bddf5a0bae85d7c28 source 633248e240b904352e66c8ff8b23a3b5f2854b69 source 9f61005dd9c4bf86e92e4c60677cf06a949a7af7 source d742c0019435d0bc90c9342492583636099a057f source 14b211478d2eded45f3e966e579a50c41325c216 source 0720c94db31d61dd9ee3c6bcd95f49003493a71b source fb497a1bd0287999819f12388c73d86f793fae76 source 148a9f29d4bbd31a1d59cb3f078f719cf09d0d90 source 3c75009a677ae950105a65c699b16caf72b516b0 source f2d2093b2198bd4c65475a60329a5a6a7a8575f1 source 64eac4e0f8f25675efe72c95df0cb17789ba3559 source c23f735eb7579477b5de3850eac075a21329c06b source 0090f1a9a3e6de84b504f21fd63d6488b17a344e source 81164892e16f7f014e32403f63ed78ba41950aec source f6fa7427858e3c9a5ac12ac30dbc99afdc066dfc source bd0825752a39644bd4da1d6ad9f18ce41e0fd5b8 source 42277cf8ad6946b9b144a3a54b5eb295188ced72 source ff4a22b003f836b9f5c8d5526d733d9d86871de0 source 32894034ea7b283d6c60cb77ef5d8b43a9c15d65 source 977a676a718bfa682352d023420f4026ea9d7025 source f62c65459100bd45bfc274e2b2587d5c6804feb2 source 7202cfa0d3bae430f8fcb8508ed389583a14539b source 5e061435a74a5461e6b9fa5a48ce44d266a3d957 source bc47d7138a8d8dd239831a38bb2eca9db13addb6 source e32c12a444e5bd0c6735db8e8008340c29a7e25e source 1118e5b986e4df8a417edcd4ee23a40fb64a0a38 source 178b361c6379bc963c8a48925f1807c583f2d09f source 13e57e42a662df76974744e916716c9f4dc9ce60 source 294967eb16a54225344ecb1913bdf85a0dc24585 source b09deb075319c1c19f91e3a6f64429b61682ebf8
? Don´t understand this sha hex... ?
(In reply to Hans-Martin Brückmann from comment #3) > ? Don´t understand this sha hex... ? Hello, status NEW means I confirmed your bug and "sha hex" is result from bisecting: https://wiki.documentfoundation.org/QA/Bibisect
Thank you
Steps to reproduce: 1. Open attached document 2. Double click on cell D4 3. Click somewhere else Observed behaviour: Rotated text disappears.
Regression introduced by: author Armin Le Grand <Armin.Le.Grand@cib.de> 2017-07-20 15:11:30 +0200 committer Armin Le Grand <Armin.Le.Grand@cib.de> 2017-07-28 17:51:56 +0200 commit e32c12a444e5bd0c6735db8e8008340c29a7e25e (patch) tree 50262efd53047ee92f5f39f9a1fd6c9e00917fc7 parent 1118e5b986e4df8a417edcd4ee23a40fb64a0a38 (diff) borderline: adaptions to primitives Handling and paint of borderlines greatly adapted to primitive usage. Solved the double paint mechanisn to no longer use the sc-local special cases. The svx tooling for borderline paint is now the only one and was extended to also handle diagonal lines. Big cleanups/removals of old paint to OutputDevice and sc-specific rendering. All other app-usages of borderline also adapted. Preparations for careful line-start/end adaption prepared and possible due to unified coordinate-system usages and basegfx class-usage Bisected with: bibisect-linux64-6.0 Adding Cc: to Armin Le Grand
Works fine for me. Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: es-ES (es_ES); Calc:
Still reproducible in Version: 6.1.0.0.alpha0+ Build ID: 8329f4541e27402d19729ae1588af8bfe61f7b49 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Same in Version: 6.1.0.0.alpha0+ Build ID: 751191ed2d7d6af6eddc3d738e8c45b0a2ab2572 CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-03-21_23:24:05 Locale: es-ES (es_ES); Calc: group
Just a repaint problem: Press CTRL+SHIFT+R to repaint and it wil reappear. This means not a problem in files or exports. But definitely ugly - triggering a repaint is missing somewhere
Adding Eike to CC. It's a repaint problem, I have no idea where calc repaints a Cell when TextEdit ends. Or what exactly goes on on repaint. I added a unrotated text in the Cell left to the rotated one, that works. So definitely has to do with rotation being active. Also happens when cursor on Cell and changing Background: Unrotated Text gets painted, Rotated Text not. @Eike: Do you have a code pointer where that text paint happens in Calc?
*** Bug 116831 has been marked as a duplicate of this bug. ***
So it appears to be painted shortly and then over-painted by the background again. Some code pointers: Drawing things happens in sc/source/ui/view/gridwin4.cxx ScGridWindow::DrawContent() called from sc/source/ui/view/gridwin4.cxx ScGridWindow::Draw() after having obtained cell infos from sc/source/core/data/fillinfo.cxx ScDocument::FillInfo() Hope that helps.
Using current master, the erros when zooming are gone. Still present is - deactivate TextEdit - change BG thus debugging into it...
Array::HasCellRotation() is wrong in these cases, thus no paint of rotated txt. Seems like not all creators of svx::frame::Array are correct yet.
Start is gridwin4.cxx:469 where a ScTableInfo is filled. In :476 goes to ScOutputData constructor, and there calls ScOutputData::SetCellRotations. Unfortunately the indices seem to be wrong, the sc/source/ui/view/output.cxx:666 call to Array::SetCellRotation *wants* to se the CellRotation, but in CELLACC (framelinkrarray.cxx:532) accesses (using mxImpl->GetCellAcc) the Cell aDummy (see framelinkrarray.cxx:256). Thus, the value is LOST. @Eike: All this indices are strange - could you have a look? Just open the bugdoc, select the cell (I think 4,4) with rotated text, change BG color using Sidebar, set BP as described above.
Looks like I have to substract nVisX1/nVisY1 in ScOutputData::SetCellRotations line 666 ?!? This seems to make it work, these are zero at full repaint (CTRL+SHIFT+R) and 0, 2 when only invalidating the single cell by changing the color...
Armin Le Grand committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=0185e65bcd73dbad2205a39369e1e06b33a2ca51 tdf#115582 Correct coordinate usage for sc's ::Array It will be available in 6.1.0. 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.
Using the latest daily build (-master~2018-05-07_00.34.00_LibreOfficeDev_6.1.0.0.alpha1_Linux_x86-64) incorporating the bug fix cured the problem for me. Thanks for your efforts in fixing this problem.
Done in latest master
(In reply to rosma from comment #20) > Using the latest daily build > (-master~2018-05-07_00.34.00_LibreOfficeDev_6.1.0.0.alpha1_Linux_x86-64) > incorporating the bug fix cured the problem for me. Thanks for your efforts > in fixing this problem. Thanks for checking. Setting to Verify! Cherry-picked to 6.0: https://gerrit.libreoffice.org/#/c/54922/
Armin Le Grand committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=08e45e11a0e74cdb4a17ec29df9d03ad03b7f7c0&h=libreoffice-6-0 tdf#115582 Correct coordinate usage for sc's ::Array It will be available in 6.0.5. 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.