Apache OpenOffice (AOO) Bugzilla – Issue 60713
connector lines should not strike out text
Last modified: 2020-02-12 07:13:48 UTC
Given two ellipses and a connector line in between. The connector line contains some text. -> The text is crossed by the connector line. It should be possible not to draw the connector line where the text is located.
*** Issue 78564 has been marked as a duplicate of this issue. ***
Shall we assign this RFE to developer?
Target reset and owner.
To work around this problem: • Select the text • Format, Character, Superscript • Uncheck the Automatic option • Raise the superscript by about 60%
Looks a lot like Issue 35747: Add option to prevent line from going through the text in lines and connectors
This _IS_ the same as issue 35747, which has had an "UNCONFIRMED" status for 10 years (wow!). ------------------- PROBLEM For clarity, the desired behavior is: 1. Draw a connector 2. Double-click it (or hit F2) to add text. Click elsewhere to finish. 3. The area occupied by the text should opaquely obscure the line. For reference, Visio has done this (by default) since the 1990s. ( edit text > right-click > "Text Block..." > Text Background : Solid Color ) I see that in OO, a connector gets its own "invisible" object frame (per the Authors User Manual - Draw Guide, in the Wiki). So, e.g., the text position is referenced to that object frame. So I see the difficulty must be that any existing opacity one might apply (if one could) would apply to the whole connector object frame. The text for the connector does not have its own frame to which to apply an opacity. -------------------- INPUT FOR DEVELOPERS It seems developers have 3 choices... 1. Add a choice in the Character dialog, probably under Font Effects, for a Font Background Color (Transparent/Opaque), with a color dropdown. -> Perhaps you could borrow the Highlighter functionality from OO Writer. There, its UI visibility is two-fold: - a "Highlighting" button on the Formatting toolbar - a Background tab in the Character dialog with a color picker palette. -> Because the text block for the connector (like any drawing object apparently) doesn't have its own object frame, though, this might end up being equivalent to option 3. 2. Add opacity functionality to the Fontwork dialog (available as a Format-category command to add to, e.g., the Drawing toolbar). It has functionality for rotating, slanting, contouring, and adding shadow (of any color) to the text. Opacity could be treated like a non-displaced, non-slanted shadow. 3. Create a new object frame (as a text frame) and open it for editing automatically when the user initiates adding text to a connector. As a separate object frame, it could be set to non-transparent and brought to front (by default). --------------------- WORKAROUNDS FOR USERS A. Workaround (effects readability but not text-area opacity): 1. Select connector; edit text (F2/double-click) 2. Right-click > "Text..." 3. Under "Spacing to borders", enter a negative Top or positive Bottom setting This is more intuitive than the proposed workaround by pesala here in 2008, and is simpler, by simply moving the text away from the line rather than altering its format. That workaround unnecessarily alters the size of the font and is less simple. B. Another workaround (effects text-area opacity, with work): (by acknak in the OO Forums in 2009 (https://forum.openoffice.org/en/forum/viewtopic.php?f=11&t=23525) 1. Select connector; edit text (F2/double-click) 2. Click on added text, drag away from connector--it's now a new Text object 3. Drag that text object back on top of connector 4. Set it to non-transparent. 5. [optionally, group with connector to keep them together]
Oops... Issue still present in ver 4.1.3.
Set latest confirmation according to comment. I do expect that it is also true for 4.1.7. Is there a reason you do not update. Are you willing to check 4.2.0?
Created attachment 86833 [details] Connector text doesn't obscure line.
Comment on attachment 86833 [details] Connector text doesn't obscure line. Just a picture of undesired behavior, for reference.
Hi... sorry for delay... Confirmed this issue is still present in 4.2.0. I tested with the Saturday Bot Build behind the link I found last Friday (rev a8115ff3c9). BTW, I generally use a deliberate security approach to software installation. So I don't update as often as some.