https://bugs.documentfoundation.org/show_bug.cgi?id=164928
Telesto <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Telesto <[email protected]> --- Principal point It's not obvious that you can define the arrow head size. The sidebar isn't communicating it. So started looking in the 'arrow' head drop down for smaller size (but didn't find any; obviously in hindsight). The line dialog didn't come to mind. It's about accessibility of the feature. And well the sidebar is the first place to look; right. Having the most used setting available at hand. I don't size arrow head size as (A) some advanced setting (b) barely to be used --- Other matter: Drawing toolbar different variations of "Lines and Arrows". Those are pre-defined line "styles"; sort of template. However not 'a style' in the sense a style in the style deck. Which is - while hammering on using styles - terrible inconsistent :-). The offering pre-defined lines and arrows, without being a actual style. --- Now lets assume: The various lines and arrows shown in the "Lines and Arrows" would be actual Styles. (A) The side-bar side-deck would - out of the be box - already raddled by styles. Becoming worse when adding a number of customizations for the various lines to be used (red line, blue arrow, different type of arrow) B) You also need to add text labels to all those styles, and find the style by label; not preview :-( C) If you designing a new arrow (as DF), which - without you realizing - matches an existing style: a warning occur that the line/arrow layout already being defined as a style; with option to convert --- Styles (in general, not specific for Draw) I'm bit allergic for pointing to styles in each and every context. Styles are - similar to templates - 'normally' used in professional setup. Corporate * Using house styles for internal or external audience. * Same sort of documents being created by dozen of employees) * Same type of document being generated thousand of times Small medium businesses (or non-profit organizations, writers) Say a user manual for peach of software: manual written by (say) a single person; audience: end-user. Manual might be updated for years by the same person (or someone else) Home user * documents generated for single use (no repeat usage) * Often for personal use, not to be published. Or only to be read by small group of people. * Documents are normally small (1-4 pages) Consequence * Setting up a whole style being pointless (not to be re-used). No interest in investing lots of time. * Quick and dirty documents. It needs to get the job done, no awards. Priority is to be functional. The essence: I except tool to be workable out of the box. Not going to many (distracting) hoops and loops. -- You are receiving this mail because: You are the assignee for the bug.
