https://bugs.kde.org/show_bug.cgi?id=522794
Noah Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INTENTIONAL Status|REPORTED |RESOLVED --- Comment #1 from Noah Davis <[email protected]> --- Thanks for the suggestion! The part that provides the current default settings for annotation tools is KQuickImageEditor, so this bug report has been moved over there. (In reply to Murz from comment #0) > The Koko edit mode seems intended mostly for simple annotation of images > like highlighting some zones, add arrows and texts. But when we annotate, > usually the Rectangle and Ellipse should be transparent, with only a colored > (red) border. Indeed, that is a common way to use the mode and those tools in Koko and Spectacle. > I can't imagine a case when the user is really needed to add a red > untransparent rectangle to the image. Hiding info (pixelate and blur are less secure), general artistic purposes and background for text (text doesn't have background settings yet). > So, to make the default settings more user friendly, let's maybe just make > the Rectangle and Ellipse tools to place transparent figures by default? I get the logic and I use them with a transparent background a lot of the time myself. I'm not sure about making this change with the current user interface though. Koko's current image editing UI is mostly copy-pasted from Spectacle's image editing UI. The current UI is a bit terse for the sake of reusing the same components for different tools and making it work well enough on low resolution screens (e.g., default virtual machine resolution). The latter was important for Spectacle. I'm concerned that if users aren't forced to do something with stroke and fill at least once, there will be significantly more users that don't learn about both of them. Annoying the user into learning the UI isn't very good, but this seems like a relatively minor annoyance. Until a better UI is implemented, I don't think this default value should change. This isn't a hard no to your idea, but I'm closing this report since I don't think it makes sense for the current UI. If I or someone else implemented a better UI, then we could revisit this. On the technical level, the default setting is provided by KQuickImageEditor. KQuickImageEditor doesn't know what the app's UI will look like, so we probably shouldn't change the defaults in KQuickImageEditor's own code. It should be possible for apps to override the default value from KQuickImageEditor, so Koko and/or Spectacle could save a different value on first run. Needing to do that might be annoying to some app devs but I consider it perfectly valid for one app using KQuickImageEditor to have different default values from another depending on their UIs and primary use-cases. -- You are receiving this mail because: You are watching all bug changes.
