https://bugs.documentfoundation.org/show_bug.cgi?id=148737
--- Comment #8 from [email protected] --- (In reply to Heiko Tietze from comment #7) Thanks for elaborations. > The parent is clearly the Line properties dialog where you start the dialog > via Add. No particular need to defend "Arrow Style" per se...but some interest to consider a broader context and another "parent": the Line tab in the Line dialog, where... ... it seems that everything is called a "style"... "Arrow Styles", "Cap Styles", "Corner Styles", and "Style" (referring to Line Styles, which has its own tab). Presumably "Line, "Arrow", "Cap" and Corner" are a "collection of attributes" that make a ??? style (what would ??? be called? can't be "line style", that label is already used). Meanwhile, in everyday speech, one might speak about "styling" a line, where the word "styles" (for the different attributes of the ??? Style) signals the existence of variations in how to "style" each attribute of a line. Perhaps it does not follow the typical "logic" of style, but it seems to work better (imo) to have consistency in the generic label to refer to the attributes ("Arrow" "Corner "and "Cap", and "Line") rather than having the Line tab refer simply to: Line Corner Arrow Cap or to use "styles" with all the attributes ("Line", "Corner", and "Cap") except for "Arrow" or "Arrowhead". Imo, those versions would "break" the connection (consistency) between the attributes. Presumably, in this case, a user notices that all relevant attributes (that can be set) are called styles. (I accept that it may not be logical in terms of formal definitions -- but it seems good psychologically to keep consistency in the general label across the attributes) -- until someone reworks the entire dialog (i.e., all the tabs in the Line dialog to remove "styles", along with the resulting implications for updating the affected help pages.) -- You are receiving this mail because: You are the assignee for the bug.
