There is a problem with the default style in Draw. It should behave as the default style in Writer, but it does not. I set Alignment > left/top, so I expect from then on, any shape, text box, drawing object will have the text left align. They do not. Not matter the default style setting, any new created text box, shape, etc. has a hard coded setting "text centered". Either I had to select any newly created shape and go to menu Format > default formatting. Either I had to reapply the default style (or any custom style) on the shape, drawing object, text box, containing text. Draw styles could benefit a little cleanup. It looks like some default or hard coded settings (as the blue default fill color of the shapes) is not optimal anymore, and could be refreshed.
Thanks for bugreport reproduced in 3.3.4 and 3.5.3 on Fedora 64 bit (on Windows not tested) reproducible in Impress and Draw in Writer and Calc behaviour the same, but there are no such category of styles
I am providing an update for this bug as it has not had one for some time. The problem as described still exists but it appears to be more complicated than indicated, with behaviour differing according to LO Draw version, object type, and associated style. I have tested this with these LO Draw / OS combinations: - v3.5.7.2 Build: 3215f89-f603614-ab984f2-7348103-1225a5b / Crunchbang v11 x86_64. - v3.6.7.2 Build: e183d5b / Ubuntu v10.04 x86_64. - v4.0.5.2 Build: 5464147a081647a250913f19c0715bca595af2f / Ubuntu v10.04 x86_64. - v4.1.2.2 Build: 281b75f427729060b6446ddb3777b32f957a8fb / Ubuntu v10.04 x86_64. - v4.1.2.2 Build: 281b75f427729060b6446ddb3777b32f957a8fb / Crunchbang v11 x86_64. For text in different objects (associated style indicated in brackets) the default alignment [Vertical|Horizontal] across all versions appears to be: - Line (Object without fill) = [Centred|Centred]. - Rectangle (Default) = [Centred|Centred]. - Text box (Default) = [Top|Left]. - Connector (Default) = [Centred|Centred]. I tested changing the alignment (toolbar button) and text anchor position (right-click > Text...) and then clicking the Update Style button in the Formatting & Styles panel to observe any effect. This required a fair amount of re-testing b/c of the Default style being shared between shapes[1], Connector, and Text box: Object without fill: - v3.5.7.2 / Crunchbang v11 x86_64 = OK - v3.6.7.2 / Ubuntu v10.04 x86_64 = OK - v4.0.5.2 / Ubuntu v10.04 x86_64 = OK - v4.1.2.2 / Ubuntu v10.04 x86_64 = OK - v4.1.2.2 / Crunchbang v11 x86_64 = OK Default (shape): - v3.5.7.2 / Crunchbang v11 x86_64 = Not OK - v3.6.7.2 / Ubuntu v10.04 x86_64 = Not OK - v4.0.5.2 / Ubuntu v10.04 x86_64 = Not OK - v4.1.2.2 / Ubuntu v10.04 x86_64 = Not OK - v4.1.2.2 / Crunchbang v11 x86_64 = Not OK Default (Text box / Connector): - v3.5.7.2 / Crunchbang v11 x86_64 = OK - v3.6.7.2 / Ubuntu v10.04 x86_64 = OK - v4.0.5.2 / Ubuntu v10.04 x86_64 = OK - v4.1.2.2 / Ubuntu v10.04 x86_64 = OK - v4.1.2.2 / Crunchbang v11 x86_64 = OK The Text box and Connector object is affected as expected when the alignment of the text is changed and then the Default style updated i.e., any new Text box or Connector (and vice versa) assumes the setting. Somewhat similarly, when updating the Default style via a shape each subsequently drawn Text box or Connector assumes the new alignment. Only shapes appear unaffected. It is also worth noting that changes to horizontal alignment (for example, via toolbar button) with a corresponding update to the Default style (for either shapes or a Connector) affects the vertical alignment of a Text box (set to Centred). This can then only be set to Top/Bottom by changing the Text anchor settings. It is all a bit confusing to be honest, but hopefully this information is useful to the developers. Bug #58492 which deals with alignment in a text box (for two different methods of drawing a text box) would appear to be related, although not necessarily a duplicate. [1] Rectangle, Ellipse, Basic, Symbol, Block Arrow, etc.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The error still exists in Version: 6.4.0.0.alpha0+ (x64) Build ID: b2d8093b19642038631dfb8f1ab6745a380a652c CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-09-23_22:42:37 Locale: de-DE (en_US); UI-Language: en-US Calc: threaded
*** Bug 66138 has been marked as a duplicate of this bug. ***
Dear nomnex, 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
It is still so, that if 'Default Style' has set vertical-anchor-top, a custom-shape, that is drag-created, has the anchor 'center' but on the same time the style 'Default Style'. If it is intended, that custom-shapes have 'center' as initial text anchor, then custom-shapes need an own initial style. Tested with Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
Dear nomnex, 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