GNOME Bugzilla – Bug 436153
dia: Minimal visual feedback when adding connection point to line
Last modified: 2019-03-20 11:30:26 UTC
Hi, a Debian user reported the following: ============================================================================ If you select a line, right click on it, and select "add connection point", you don't get any obvious visual feedback that something has happened. There is a little (tiny!) faint blue "x" that appears, but it is so small that it can easily be lost. This problem is especially severe when the line width is about half of the size of the "x". Needless to say, this problem is especially severe with thick blue lines, especially colors near #1095D8. I'd suggest three changes: 1) the connection point color be chosen not to match the background or the line color. 2) The connection point should be highlighted or bold or bigger for a moment when it is first created, 3) The connection point size be made adjustable (if it isn't already), and the default be made a little bigger. ============================================================================ I can understand this, especially for non-rectangularly-pixel-grid-aligned lines like pixel-step-lines. See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405831
I'd suggest, rather than making the connection point sizes adjustable (ok maybe add an option in the preferences to adjust the default percentage), make their size a percentage (e.g. 200%) of the line width, to ensure visibility.
Idea 2) would require a highlighting of connection points that not currently a part of Dia. It's been requested before that connection points be more visible for accessibility, and suggestion 3) would fit nicely with that. I prefer to have connection points be a consistent color, so 1) is not the best, though a shade or edge might help.
marking enhancement
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dia/issues/193.