[ghostwriter] [Bug 476853] New: Markup doesn't accept non-anglican characters
https://bugs.kde.org/show_bug.cgi?id=476853 Bug ID: 476853 Summary: Markup doesn't accept non-anglican characters Classification: Applications Product: ghostwriter Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: ohy...@disroot.org Target Milestone: --- Words ending in Å, Ä or Ö are not correctly rendered when put within Markdown symbols like for bold "**text+å**" *** STEPS TO REPRODUCE 1. Write a word ending in "å" 2. Try to use **+** to make it format to bold text OBSERVED RESULT The markdown presents as "not bold" text. If you remove the foreign symbol it does turn to proper markdown rendering EXPECTED RESULT That markdown should show correctly SOFTWARE/OS VERSIONS Linux: Garuda Linux Latest Plasma ADDITIONAL INFORMATION Key here is that like many who do not speak English natively I have my system set to use English as a language to make it easier to repair or fix small bugs (searching in English provides more results). So Ghostwriter may perhaps see my native use of å, ä and ö as foreign characters not to be included. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441351] New: Gwenview should display Krita's .kra files
https://bugs.kde.org/show_bug.cgi?id=441351 Bug ID: 441351 Summary: Gwenview should display Krita's .kra files Product: gwenview Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: j...@ohyran.se Target Milestone: --- SUMMARY Currently Gwenview offers a wealth of image formats to display - but Krita's .kra files aren't one of them which is a shame considering that both are in the KDE camp and it would be a rather nice way to sort, organize and handle Krita workfiles. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 429711] New: Shortcut for "Clear Notifications"
https://bugs.kde.org/show_bug.cgi?id=429711 Bug ID: 429711 Summary: Shortcut for "Clear Notifications" Product: frameworks-knotifications Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: j...@ohyran.se CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY A way to easily clear all notifications OR some by the use of a keyboard shortcut. The button for removing all notifications is too hidden and doesn't seem to have a keyboard centric alternative STEPS TO REPRODUCE 1. Receive plenty of notifications 2. Open the systemtray 3. Click button for "notifications" 4. Find the little "Sweeper" button 5. Click that 6. No Notifications OBSERVED RESULT Fiddly to click if you often don't use a mouse and annoying if you have a lot of notifications you don't care about in a long list EXPECTED RESULT A quick shortcut to "clear all" or that and one for "Clear all low priority" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428874] Sidebar OR main KCM view Blacked Out (Nvidia)
https://bugs.kde.org/show_bug.cgi?id=428874 --- Comment #4 from Jens Reuterberg --- (In reply to Nate Graham from comment #3) > Supposedly fixed in the latest version of the Nvidia driver. Thank you! Sry I dug like crazy to make sure it wasn't a duplicate - my bugzilla game isn't all there -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428874] New: Sidebar OR main KCM view Blacked Out (Nvidia)
https://bugs.kde.org/show_bug.cgi?id=428874 Bug ID: 428874 Summary: Sidebar OR main KCM view Blacked Out (Nvidia) Product: systemsettings Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@ohyran.se Target Milestone: --- SUMMARY Opening the Systemsettings shows either the main view and a black sidebar (which can't be clicked) or if you open a specific KCM, the sidebars and the main kcm is blacked out. STEPS TO REPRODUCE 1. Open System Settings from Krunner, Konsole or Kickoff 2. - OBSERVED RESULT Sidebar Blacked out if you launch systemsettings, active KCM blacked out if you launch that KCM specifically. EXPECTED RESULT That they are visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed 20201106 (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Nvidia Driver 450.80.02 Kernel: 5.9.1-1-default This is after installing the proprietary Nvidia drivers and I vaguely expect that to be the issue hence including Kernel and Nvidia Driver version. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428874] Sidebar OR main KCM view Blacked Out (Nvidia)
https://bugs.kde.org/show_bug.cgi?id=428874 --- Comment #1 from Jens Reuterberg --- When launched from Konsole this is the output: Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" QQmlEngine::setContextForObject(): Object already has a QQmlContext QQuickWidget: Failed to make context current QQuickWidget::resizeEvent() no OpenGL context QQuickWidget: Failed to make context current QQuickWidget: Attempted to render scene with no context Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/share/kpackage/kcms/kcm_kscreen/contents/ui/Panel.qml:137:13: Unable to assign [undefined] to int file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:141:21: QML PrivateActionToolButton: Binding loop detected for property "checkable" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QQuickWidget: Attempted to render scene with no context QQuickWidget: Attempted to render scene with no context QQuickWidget::invalidateRenderControl could not make context current -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428267] When notifications are turned off - Audio raise/lower still makes noise
https://bugs.kde.org/show_bug.cgi?id=428267 Jens Reuterberg changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428267] When notifications are turned off - Audio raise/lower still makes noise
https://bugs.kde.org/show_bug.cgi?id=428267 --- Comment #4 from Jens Reuterberg --- It seems like the issue was more confusion with how the volume for applications worked. Closing this bug for now and may reopen if I get more info from the user -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428267] When notifications are turned off - Audio raise/lower still makes noise
https://bugs.kde.org/show_bug.cgi?id=428267 --- Comment #3 from Jens Reuterberg --- (In reply to Nate Graham from comment #2) > Technically these aren't notifications. You can turn off audio volume > preview in System Settings > Audio > Applications > Notification Sounds > > click the mute icon. In fairness this bug report is from a user who contacted the Facebook account who felt they wherent good enough with english to report the bug themselves and didn't understand how to do it. Their argument was that during video meetings they turn off all sounds to not disturb the conversations but then when raising/lowering the volume the clicks still made noises and that felt "off" and annoying since their logic was that when not wanting any sound notifications, all sound notifications should be removed. The reason I added it is because in a way the logic felt appealing to me and I didn't know if it was intended or not. The reason why is because that users action makes total sense - what from that person POV differentiate the clicks for lowering or raising volume to say, battery charging? The noise the volume raise action make is there to show the user the level of volume, the noise the power cord connection makes also tells them something. At the same time as mentioned its two different things but to the user this felt strange and they thought it was a bug. So I think its worth considering - they are different technically, but in practice they are in some scenarios, not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428267] New: When notifications are turned off - Audio raise/lower still makes noise
https://bugs.kde.org/show_bug.cgi?id=428267 Bug ID: 428267 Summary: When notifications are turned off - Audio raise/lower still makes noise Product: plasmashell Version: 5.20.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: j...@ohyran.se CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Currently the audio notifications, when turned off, still gives an audio notification when volume is raised/lowered, it can be turned off by going in to audio settings and unclick the audio volume for the raising/lowering of volume - but with online meetings it would make more sense to go in to Notifications and turn them off. This may also be a regression as this was possible in 5.19 STEPS TO REPRODUCE 1. Go in to Notification Settings 2. Turn off Notification Sounds 3. Raise or Lower the Volume OBSERVED RESULT The volume raise/lower makes a click sound, unless shut off in the Audio Settings for the widget. EXPECTED RESULT That all notifications get silenced when notifications are turned off SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tested on Opensuse TW and Arch (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION Same effect on Arch Linux. The tricky part is I suppose what notifications are critical and what are seen as "flair" - volume feels like it should make a noise, but in Video meetings it is distracting. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418575] Missing an icon for reply (chat, not mail)
https://bugs.kde.org/show_bug.cgi?id=418575 Jens Reuterberg changed: What|Removed |Added CC||j...@ohyran.se --- Comment #1 from Jens Reuterberg --- Something like this? https://i.imgur.com/qmteqxu.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #7 from Jens Reuterberg --- Created attachment 131271 --> https://bugs.kde.org/attachment.cgi?id=131271=edit Centered 32x32 icon Centered as per HIG specs 32x32 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #6 from Jens Reuterberg --- Created attachment 131270 --> https://bugs.kde.org/attachment.cgi?id=131270=edit Second version of Emacs org mode 64x64 with centered unicorn Centered the unicorn as per specs from HIG -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #5 from Jens Reuterberg --- Added 16x16 and 32x32 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #3 from Jens Reuterberg --- Created attachment 131268 --> https://bugs.kde.org/attachment.cgi?id=131268=edit 16x16 Emacs Org mode icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #4 from Jens Reuterberg --- Created attachment 131269 --> https://bugs.kde.org/attachment.cgi?id=131269=edit 32x32 Emacs Org mode icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 --- Comment #2 from Jens Reuterberg --- I made a suggestion for an icon (org mode icon suggestions) its just 64x64 would it work? Looks like this https://i.imgur.com/TgEBDiC.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425836] Request icon for Org documents
https://bugs.kde.org/show_bug.cgi?id=425836 Jens Reuterberg changed: What|Removed |Added CC||j...@ohyran.se --- Comment #1 from Jens Reuterberg --- Created attachment 131267 --> https://bugs.kde.org/attachment.cgi?id=131267=edit Org Mode icon suggestions -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368827] Using the KWin Resize keyboard shortcut, all keypresses are sent into the window during the resize
https://bugs.kde.org/show_bug.cgi?id=368827 Jens Reuterberg changed: What|Removed |Added CC||j...@ohyran.se -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399665] Breeze drawing tool tool icons need improvement
https://bugs.kde.org/show_bug.cgi?id=399665 --- Comment #3 from Jens Reuterberg --- So looking around this bug using Cuttlefish there are some really easy fixes Textfield: replacing the tool-text icon with the draw-text icon would fix for example the "text" symbol in Kolourpaint as it actually as a large T in it or better yet something like xml-text-new, the icon Kolourpaint uses is inherited from document editors which isn't ideal for a drawing app since there you don't really automatically assume its going to be "text" there) To moderately complex ones Selection Symbols: Improving sizeing of the lassoo symbol in tool_free_form_selection with its too narrow dots that blend together. bigger dots to emphasize it COMBINED with adding dots to the selections fields in tool_elliptical_selection and select-rectangular icons would make it more clear that, yes this is selection - the dotted border is basically shorthand for it anyway so might be worth while in general. (select-rectangular should be looked into a bit more, the added complexity with the pen is not useful in most scenarios and could be replaced with a dotted rectangle and the handles (like tool_elliptical_selection)) Polygon: The polygon symbol is filled in, the circle, the square and the rounder corners square (which should be slightly more square in my eyes to be readable) are not making them look unrelated. Swapping the polygon one for the "connected lines one" would make them look related and make more sense over all Connected Lines: This needs a completely new icon, preferrably based off of "Curve" - something like lines-connector might work but with more "zigzag" to it. ' The the damn fiddly things... Zoom: We need a better zoom symbol language or at least some kind of fallback for simpler applications - the current ones we have are made for professional apps and often miss the mark even if they are relevant and critical in those apps. A simple "search" symbol with a plus connected as per icon specs would fit nicely. (this is a bigger issue as the dotted lines appear in many zoom icons which makes sense based on what apps they where made for but as those icons are often fairly wide in range they tend to be used badly and looking at replacing zoom might be worth while) I think color selector (the drop) should stay as that is used in a lot of different apps and work as intended there. It's a skip and a jump for new users who use Kolourpaint perhaps but not that complex -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399665] Breeze drawing tool tool icons need improvement
https://bugs.kde.org/show_bug.cgi?id=399665 Jens Reuterberg changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #2 from Jens Reuterberg --- I think improving the icons as is for Kolorpaint might be a good thing, removing an entire icon language (with clear and well known benefits) would be bad (for a wealth of other applications). Perhaps check out how apps like Inkscape work with Breeze (which it does expertly) and mimic that for Kolorpaint would be a way forward? Just adding colour in this scenario would be taking the easiest path forward and instead of improving something - wrecking it. So I suggest looking at improvements for those icons - and if that is impossible - accept that we will destroy a complete icon language for one app. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393202] Clipped text in sidebar view only
https://bugs.kde.org/show_bug.cgi?id=393202 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #2 from Jens Reuterberg <jens...@kolabnow.com> --- Same thing for me, same setup as isalliswell. Have tried swapping around fonts but so far nothing changed when doing that -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 386895] dialog-password grossly oversized in gtk3
https://bugs.kde.org/show_bug.cgi?id=386895 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #2 from Jens Reuterberg <jens...@kolabnow.com> --- Well I would see this as a Breeze-Icon theme bug since we don't have a "dialogue-password" symbolic icon (as far as I can see the others in the toolbar are symbolic icons). Lemme mark this email as "important" and make a symbolic icon for the theme and ping Andreas Kainz to see if he can throw it in there and if that helps it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386656] [Feature request] Circular avatar
https://bugs.kde.org/show_bug.cgi?id=386656 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #4 from Jens Reuterberg <jens...@kolabnow.com> --- Well a circle avatar is already possible. The dark avatars for example (konqi, penguin, zebra) are nothing but PNG images with transparency (done in GIMP iirc and you can do that now by placing a circle around whatever image you want and then cropping the image, saving it as a PNG with transparency (which creates a square image but with content only within the circle) and loading that from file). I think removing the option to have both is not a good way to go - instead being able to set "round" or "square" may be relevant but that should be a technical decision as it's pushing demands for further options to the devs. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384591] [icon request] tray icon for qBittorrent
https://bugs.kde.org/show_bug.cgi?id=384591 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #4 from Jens Reuterberg <jens...@kolabnow.com> --- There is one more in Breeze too right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 --- Comment #36 from Jens Reuterberg <jens...@kolabnow.com> --- Checking into it and it can be a rendering issue, that depends on Qt - and if so (this is based on random asking around, searching for the issue online so "means nothing") its based on certain font types (like clear sans) and/or formats of fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #35 from Jens Reuterberg <jens...@kolabnow.com> --- The only way this is related to QML, Qt or Plasma is if we somehow force a wider gap between upper and lower case letters in the example provided (H and i). I don't understand why we would or why that would be visible only in a few fonts. Not saying its impossible but it feels like a fault that is only fixable by the font designer or the version of the font you downloaded. If not this would be rather easily spotted in ALL fonts -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385048] GNU Octave svg logo looks ugly, please use official one.
https://bugs.kde.org/show_bug.cgi?id=385048 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #1 from Jens Reuterberg <jens...@kolabnow.com> --- I prefer ours and if we should switch, it shouldn't use the official one as it is not good enough. If there is someone willing to provide an alternative that is entirely up to Andreas K if he wish to switch. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384357] Breeze theme Task Manager icon for Virtualbox is ugly, nondescript, doesn't match what's shown in the Task Switcher, and departs entirely from the real VirtualBox icon's general
https://bugs.kde.org/show_bug.cgi?id=384357 --- Comment #7 from Jens Reuterberg <jens...@kolabnow.com> --- Created attachment 107760 --> https://bugs.kde.org/attachment.cgi?id=107760=edit Rough for icon Just a rough example to see if its still recognizable as the VM icon (its not much to on in it) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384357] Breeze theme Task Manager icon for Virtualbox is ugly, nondescript, doesn't match what's shown in the Task Switcher, and departs entirely from the real VirtualBox icon's general
https://bugs.kde.org/show_bug.cgi?id=384357 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #6 from Jens Reuterberg <jens...@kolabnow.com> --- (In reply to Nate Graham from comment #4) > In fact, if we simply delete virtualbox's custom icon from the Breeze theme, > the issue goes away, IMHO. The existing icon is bold and flat, just like > other Breeze theme icons. It fits in perfectly, no custom icon needed. The upstream icon in current version isn't good enough and would have to be replaced with something that follows the standard. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #30 from Jens Reuterberg <jens...@kolabnow.com> --- Yes thats my bottom line as well and it has been since Plasma 5.0 and we got involved in it AND its the reason Breeze Icons, and colours, etc constantly evolve. Take your bug about the server rack - THAT is where I think we should have made it more simple. The icon you refer to is someone trying to draw a server rack (succesful or not is irrelevant, check it in Cuttlefish, its pretty realistic). Instead we should have simplified it. Made it a symbol instead of an image. Either way, talk to you more in the #kde-vdg channel? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #28 from Jens Reuterberg <jens...@kolabnow.com> --- Also just to clarify: I am not at all saying "you are wrong" or anything like that. Just that this discussion is at an impasse. We can only improve the Breeze icon theme, we wont change the design language underneath. As you say "people power" is lacking - and I wish, honestly, that I could say that Oxygen Would get better support soon but like you it seems less likely. (which also is the reason this discussion is relevant since your options shrink effectively). One hopeful fix would be that we could have better sorting and grading of KDE icon themes. I KNOW there are some for example Mac like themes out there that could work for you but in the current state of Get Hot New Stuff its a mess to find. (If you have more questions you can try to catch us in the #kde-vdg room on freenode (Im jensreu)) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #27 from Jens Reuterberg <jens...@kolabnow.com> --- Sry you are right "click bait" is a strong term. It's just that in my circles its sort of like when people say "thats skeumorphism!" while pointing at for example beveled buttons and how that becomes a truth used to slap down good design practices. The statements within it is already well known and have been for a very long time and is something that most of us work towards. Those fixes are layout and indicators. Essentially what is being said in the text isn't close to being as dramatic as the header. This isn't a "flamewar". Simplified design, vs realistic Design (skeumorphism is the mimicing of real world objects and can be equally true in simplified as in realistic design) is not a "flamewar" - at a certain point both styles have benefits - in one certain things are more easily done, in another other things are more easily done. Both come with drawbacks and demands. Both of these "schools" (lets say) and their demands are well known. Breeze is constantly improving and changing - but it wont change its design language to follow fads or subjective preferences. That is better served either by a fork, or by another icon theme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #24 from Jens Reuterberg <jens...@kolabnow.com> --- Paul: if you don't want people to take it to heart then why post that clickbait article in a bug list? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #20 from Jens Reuterberg <jens...@kolabnow.com> --- The reason other icons are there is because the Get Hot New Stuff is linked to a webpage which is not directly controlled by KDE that used to be called KDE look, and which was mirrored by sites like gnome-look and openbox-look etc. That means that many of the icon themes are in fact GTK icon themes and, as you noticed, unsuitable for KDE (this is the confusing part of KDE look and Get Hot New Stuff - its not communicated clearly enough that this is a third party area and not something native) The elementary theme Andreas mentions is the one called Elementary-KDE in Get Hot New Stuff -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384129] Rename colors from British to American English
https://bugs.kde.org/show_bug.cgi?id=384129 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #1 from Jens Reuterberg <jens...@kolabnow.com> --- "In this class we learn English, not American" as my old English teacher used to say. The choice of names for colours are most probably my fault simply because that is how I spell them. "Grey", "Colour", "Aluminium". But its potato/potato as far as I am concerned -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 381288] Breeze could use higher-contrast text by default (tweaked color scheme attached)
https://bugs.kde.org/show_bug.cgi?id=381288 --- Comment #7 from Jens Reuterberg <jens...@kolabnow.com> --- You do have a good point. Perfect black on light-light grey is the preferred one... (although as a print-monkey I need to say "Bright Yellow on Dark Grey" or the other print monkeys may get angry ;) ) I worry about the inverted colour scheme though and icon effects. I propose this - lets create a secondary theme and then try to do some proper testing. I mean the tricky bit is tying up the bag as it where (because we don't want #00 background for breeze dark) as the colour scheme is such a huge chunk of the identity in so many other areas (from mascots to print material, webpages etc) - will the gain from swapping to #00 in readability justify eventual issues there? Or am I just bikeshedding? We also need to see if we are creating a huge problem for the developers in the future... so we would need to have a dev in on it to supervise so we don't create a mess Sebas (et al) can we sort of hold off on this while we drag poor Nate into the VDG room for a chat? On Sunday, 18 June 2017 15.42.54 CEST Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=381288 > > Nate Graham <pointedst...@zoho.com> changed: > >What|Removed |Added > > Status|RESOLVED|UNCONFIRMED > Resolution|WONTFIX |--- > > --- Comment #6 from Nate Graham <pointedst...@zoho.com> --- > Thanks for the comments, everyone. > > I have to disagree that this is a matter of subjectivity or taste--this is > just my preference and other people might not like it. There are objective, > scientifically derived principles governing things like eyestrain and > readability: > > https://www.nngroup.com/articles/low-contrast/ > http://www.tinhat.com/usability/color.html > http://contrastrebellion.com/ > http://universalusability.com/access_by_design/text/contrast.html > > From the above articles, you can see that the *most* readable, usable text > is 100% black on a not-quite-100%-white background, since pure white can be > blinding on bright screens. Breeze is *so close* with the pleasant light > gray backgrounds, but the text itself needs to be a bit bolder to reap the > rewards of maximum readability. This will not present a "harsh" contrast; > on the contrary, it will make the text *more attractive*, not less. Again, > this is not my personal preference, but rather the result of decades of > hard-earned usability investigation. I encourage you to read those > articles. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 381288] Breeze could use higher-contrast text by default (tweaked color scheme attached)
https://bugs.kde.org/show_bug.cgi?id=381288 --- Comment #5 from Jens Reuterberg <jens...@kolabnow.com> --- I have to agree with Sebas here: the choice is a "damned if you do, damned if you don't level" - the harsh contrasts would make many users feel as if the experience is worse... I am not trying to wave you away of course - you are more than right there are many users who find the theme too vague but as there is a contrast colour scheme of Breeze Dark it feels as if its kinda covered. On Friday, 16 June 2017 17.46.16 CEST Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=381288 > > Nate Graham <pointedst...@zoho.com> changed: > >What|Removed |Added > > CC||pointedst...@zoho.com > > --- Comment #3 from Nate Graham <pointedst...@zoho.com> --- > It's worth mentioning that reviewers have noted Breeze's lack of sufficient > text contrast. For example: > http://www.ocsmag.com/2017/02/17/the-state-of-plasma/ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379861] The Kontact icon is a wifi icon
https://bugs.kde.org/show_bug.cgi?id=379861 --- Comment #2 from Jens Reuterberg <jens...@kolabnow.com> --- Its based on the RSS and old Akregator icon which, when in monochrome becomes very "wifi icon" like (mostly because Wifi icons tend to be "anything with a signal symbol in it"). One idea would be to change the Akregator icon from scratch and remove the focus on the RSS symbol (the thing that looks like a wifi thing) On Tuesday, 16 May 2017 19.15.08 CEST Daniel Vrátil wrote: > https://bugs.kde.org/show_bug.cgi?id=379861 > > Daniel Vrátil <dvra...@kde.org> changed: > >What|Removed |Added > > Component|general |Icons > Product|kontact |Breeze > Version|5.5.1 |unspecified >Assignee|kdepim-b...@kde.org |visual-des...@kde.org > CC||dvra...@kde.org, > >||kain...@gmail.com > > --- Comment #1 from Daniel Vrátil <dvra...@kde.org> --- > I think you are referring to Akregator (RSS feed) icon, which looks like > wifi icon tilted by 45 degrees. This is an icon provided by Breeze, not by > Akregator, so reassigning to Breeze. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #1 from Jens Reuterberg <jens...@kolabnow.com> --- For clarity of the icons - I am not a big Krusader user myself so just want to ask some (perhaps obvious) questions concerning the usage so we don't make icons that are more confusing than anything else. Show Equal Files - would an equal sign be clear enough or would for example an "equal sign within a document" make more sense (or less)? Show Unequal Files - should share some kind of similarity with the Equal Files icon so that both are "connected" in my logic (which is why say a document or file symbol with an equal/unequal sign in it would make more sense in my mind). But maybe that would be muddling the understanding of it. Swap - since that might look like a "reload" icon would say a line in the middle or something that represent the two panels make sense? Am I way of base in this thinking? On Mon, May 8, 2017 at 9:33 , Alex Bikadorov <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=379638 > > Bug ID: 379638 >Summary: Icon request: equal, unequal and swap >Product: Breeze >Version: unspecified > Platform: Other > OS: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: Icons > Assignee: visual-des...@kde.org > Reporter: alex.bikado...@kdemail.net > CC: kain...@gmail.com > Target Milestone: --- > > The Krusader project needs three icons: > * equal: a simple "=" sign as icon, monochrome colours > * unequal: the mathematical unequal sign (equal combined with a > slash), > monochrome and additionally in red if this is not too much work > * swap (sides): a double arrow "<->", monochrome > > Background/Usage: Krusader file synchronizing feature > * equal: show identical files > * unequal: show differing files > * swap: swap the panel sides > > All of them might be useful for other applications. > > Thank you! > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378606] Please replace those childish avatar images
https://bugs.kde.org/show_bug.cgi?id=378606 --- Comment #5 from Jens Reuterberg <jens...@kolabnow.com> --- I'm not entirely certain which are the "technical" ones you refer - is it the B/W then thank you I made them. I rather disagree with you except on one point - the default avatar - I think that was just chosen more or less at random at the time and was the stock/base out of which the "famous people" avatars where made (Gandhi, Da Vinci etc) That leaves us with the issue of which one to chose. B/W penguin? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378606] Please replace those childish avatar images
https://bugs.kde.org/show_bug.cgi?id=378606 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #3 from Jens Reuterberg <jens...@kolabnow.com> --- We have a rather eclectic mix of avatars to chose from http://i.imgur.com/eOZn8D8.png , anyone can suggest more images if they want to. We are serious. Any distro can, if they choose, define WHAT kind of user they prefer. If you want to stick to "as serious as possible" you can just keep the B/W avatars. You can even remove every single avatar except one or two that you prefer. We are a DE, we don't tell distros what they're user group should be and we have added up a few avatars that we felt like doing - our job is to ensure that. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 374300] Option to change the font color on the lock screen
https://bugs.kde.org/show_bug.cgi?id=374300 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #1 from Jens Reuterberg <jens...@kolabnow.com> --- Currently the only option is to change the wallpaper you use (either by modding it to include lighter sections in the area where the dark text is or changing it entirely). The issue isn't that there is anything blocking a way to set it from a design perspective but rather where to include it currently and how hard it is to do from a technical standpoint. We have a massive problem with settings - and there has been quite the discussion about SDDM/Lockscreen/Wallpaper-settings which will probably affect this. Adding it in the "set wallpaper" section for Lockscreen and SDDM seems like a good temporary solution (since they are mostly empty space currently) but then again what will happen with the work when those are redesigned? TL;DR from a design perspective nothing blocks the idea that you can change font colour - at the same time, the programmers will have to reply on how complex it is to add - and whether the risk of a future overhaul will make that effort worthless. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373668] Tiny keyboard layout indicator is the Lock Screen
https://bugs.kde.org/show_bug.cgi?id=373668 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #8 from Jens Reuterberg <jens...@kolabnow.com> --- Ok I think this discussion needs to mellow out a tad... BACKGROUND TO CURRENT PLACEMENT: The assumption was that the users who did need it would find it, where as the users who didn't need it wouldn't have the entire screen muddled up with different controls. This in combination with the motivation to make the act of starting and shutting down feel like one unified whole instead of different aspects of the DE handing over to each other. Now that was designed slightly before the fact that the keyboard layout isn't visible if you don't have another keyboard layout installed - which sorta turns the tables. That leaves another issue - will putting every single control on prime real estate solve the issue? It will for you (Anton) because that is what you personally need - but will it do that for all or will that as well as the switcher for different DE's (which would then have to be moved as well) just clog up the controls? WHAT TO DO: Looking at SDDM - the key task there is to fill in your password (which is why its centered). The second task is to switch users, the third is to shut down the computer, reboot etc. The date/time is there to ensure the similarity between the login and the lock screen visually. So whatever we change here - will affect the design of Lock Screen, etc. There is a future addon for the lock screen (not SDDM) where you can control the music player and that will be placed in the center column of the lock screen but underneath. We could dedicate that area to it BUT that may also result in some issues like a TON of stuff clogging it up. Making the buttons bigger would be interesting but that wont fix much either in the long run since the reason they are pushed away to the sides is to 1) get them out of the way as not being universally relevant objects and 2) get some kind of balance (and not make it look like a middle school book report (center aligned text everywhere)). So what we need is something that not only displays the lesser relevance of the keyboard layout in comparison with login etc - but also balances it out. TL;DR its an issue, but a slightly fiddlier one than one may think -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371914] Icon request: Claws-mail
https://bugs.kde.org/show_bug.cgi?id=371914 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #2 from Jens Reuterberg <jens...@kolabnow.com> --- Made an icon for it, its not perfect as on smaller sizes the rounded shape of the claw looks kinda blurry, so it looks like a batch of agave growing in an envelope but its up to the icon team what they think. http://imgur.com/a/vvrOE -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370374] GRUB menu has huge lag due to theme
https://bugs.kde.org/show_bug.cgi?id=370374 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #10 from Jens Reuterberg <jens...@kolabnow.com> --- I'm interested whether this effect is true when using other grub themes? Because if it is, it's something way bigger than KDE/Plasma and something that would make sense to ask around about since many distros and DE's also provide their own themed grub. If on the other hand it isn't then obviously something is terribly wrong in OUR grub theme that needs figuring out. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370358] GIve sddm user home folder and .face.icon ACL rights in order to load the avatar
https://bugs.kde.org/show_bug.cgi?id=370358 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #4 from Jens Reuterberg <jens...@kolabnow.com> --- Can confirm that it's the same on a newly installed Arch machine here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369671] Tone down transparency of kicker/kickoff menu
https://bugs.kde.org/show_bug.cgi?id=369671 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #4 from Jens Reuterberg <jens...@kolabnow.com> --- One way to solve this would be too turn off transparency completely when Blur/Background Contrast isn't enabled (for applauncher as well as panel etc) - but then again there are a few people who use it simply as is and I have no idea how tricky it is to create such a solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #18 from Jens Reuterberg <jens...@kolabnow.com> --- (In reply to Marco Martin from comment #6) > this bug is pretty much mutually exclusive with > https://bugs.kde.org/show_bug.cgi?id=353834 > I fear icons are either going to be too big for some people or too small for > some other people (and i don't want to add a configure icon size ui) I guess that any variant will rub some people wrong. We simply can't account for all tastes and any change will make one group or another angry. The question is: which group do we want to piss off, or do we accept the problems that come with such a configuration UI. Also if Guillame is correct above, that HiDPI screens make the icons stick to 16x16, that's the main issue since that would make them close to unusable. One solution would be to create a third size of 32x32 icons and simply skip to that size when the panel is resized to something that could accomade them. But that means recreating the icon theme (so its pixel aligned) and that will take a while (IIRC only a few of the panel icons exists in 32x32) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358578] Active window taskbar entry background too bright in Breeze Dark theme
https://bugs.kde.org/show_bug.cgi?id=358578 Jens Reuterberg <jens...@kolabnow.com> changed: What|Removed |Added CC||jens...@kolabnow.com --- Comment #7 from Jens Reuterberg <jens...@kolabnow.com> --- I can't reproduce this now as in Breeze Dark the window decorations are both dark. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365318] KRDC is unreadable under breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=365318 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #12 from Jens Reuterberg <ohy...@gmail.com> --- Neither Okular, k3b or ktorrent are affected by what gtk theme you use though... unless you have set the KDE themes to pick up the GTK theme - which looking at it seems unlikely. With the GTK theme there is a generation shift that happened quite recently (and may not have picked up) where GTK3 apps suddenly didn't work with the old GTK3 theme. But that seems like it's not whats happening at all (that glitch just messed with rightclick menu's being white-on-white). What happens when you set the entire destop via Look n Feel to "Breeze Dark" and then go to GTK theme, set that in turn to Breeze Dark (and Breeze Dark Icons) - then do the log-in-log-out dance? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue
https://bugs.kde.org/show_bug.cgi?id=365267 --- Comment #4 from Jens Reuterberg <ohy...@gmail.com> --- (In reply to Thomas Lübking from comment #3) > Sounds much more like a plasmashell issue - shell and compositor seem to be > running on the screenshots. Ah cheers Thomas (it was five in the morning and I had slept two hours when I did this bugreport so a bit saucy in the head) Also the same applies to my desktop, tested it there to, will test it on another distro as well later to see if it exists there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365270] New: Alignment in digital clock/calendar popup wrong
https://bugs.kde.org/show_bug.cgi?id=365270 Bug ID: 365270 Summary: Alignment in digital clock/calendar popup wrong Product: plasmashell Version: 5.7.0 Platform: Archlinux Packages URL: https://imgur.com/eH6oPt4 OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Digital Clock Assignee: mklape...@kde.org Reporter: ohy...@gmail.com CC: plasma-b...@kde.org The digital clock calendar is awesome but it is also very very misaligned due to width changes between the letter/numbers practical width and font width. This causes the effect that it looks extremely misaligned even though the two parts of the calendar are perfectly aligned. (Saturday - compared to July for example appear to be on entirely different top lines but the "saturday" is connected to the "09" which due to the size of the font has a rather massive padding and pushes "saturday" down) Similarly the "no events today" sign is based on the initial size and placement of the date number which makes it in turn misaligned with the right hand part of the calendar [screenshot in link] Reproducible: Always Steps to Reproduce: 1. Open Calendar Actual Results: Alignment appear wrong Expected Results: Alignment should not appear wrong - one method to achieve this is to base the placement of "july" in the actual calendar bit on the right to be linked to the top edge of the 09 as well, which in this case would sadly create a rather large padding on top. But by decreasing the font size of the "09" this could be minimized. The "no events today" should be placed centred in the open area of the calendar daily planner from bottom row of date to bottom of widget. Or if possible centered horisontally, but aligned with middle bar of the actual calendar on the right. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364329] System forgets custom login screen background image
https://bugs.kde.org/show_bug.cgi?id=364329 --- Comment #2 from Jens Reuterberg <ohy...@gmail.com> --- For me this is using Arch based distro so it is distro independent -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364329] System forgets custom login screen background image
https://bugs.kde.org/show_bug.cgi?id=364329 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #1 from Jens Reuterberg <ohy...@gmail.com> --- I have the same issues on 5.6 and 5.7 - the reason I think is because when you select an image from your own home filesystem SDDM can't reach it, picking a file in /usr/shr and it happily accept the change. The best way for me have always been renaming the image you want to use and moving it manually to the SDDM theme you select and renaming it background.png (thereby removing the standard background.png) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365269] New: Widget Explorer lacking icons
https://bugs.kde.org/show_bug.cgi?id=365269 Bug ID: 365269 Summary: Widget Explorer lacking icons Product: plasmashell Version: 5.7.0 Platform: Archlinux Packages URL: https://imgur.com/NFrzT9f OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: ohy...@gmail.com Icons for several widgets in the Widget Explorer are blank and display the "no-icon" icon. Reproducible: Always Steps to Reproduce: 1. Rightclick Desktop 2. Click Add new widget Actual Results: Widget icons are removed for several widgets Expected Results: Visible icons for all widgets. The icons for the widgets are available in cuttlefish as for as I can tell. Activity Pager, Media Frame and KDE connect for example -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue
https://bugs.kde.org/show_bug.cgi?id=365267 --- Comment #2 from Jens Reuterberg <ohy...@gmail.com> --- More fiddling - this only affects the system tray widget and when its on the desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue
https://bugs.kde.org/show_bug.cgi?id=365267 --- Comment #1 from Jens Reuterberg <ohy...@gmail.com> --- After doing it over and over I realize the only thing that it removes is the wallpaper, all other features like opening new apps. yakuake, krunner etc are all there. There simply isnt a desktop to rightclick on or interact with in any way Rightclicking on the system tray on the desktop still brings up the desktop settings and not just clicking the settings on the panel -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365267] New: Kwin crashes after adding a new system tray and moving it, displays wrong dialogue
https://bugs.kde.org/show_bug.cgi?id=365267 Bug ID: 365267 Summary: Kwin crashes after adding a new system tray and moving it, displays wrong dialogue Product: kwin Version: 5.7.0 Platform: Archlinux Packages URL: https://imgur.com/a/D0bfY OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ohy...@gmail.com I had a panel on one side with a system tray, launcher and clock. Added a new system tray to desktop and when clicking the settings button, I get the desktop settings instead of system tray settings. When trying to drag the system tray widget using the handle, kwin crashes, screen goes black but still display mouse, and dialogues like desktop number when moving from desktop to desktop. Reproducible: Always Steps to Reproduce: 1. Add system tray to desktop 2. Click on settings for the applet (not rightclick on system tray) 3. Move system tray Actual Results: Displays the desktop settings instead of widget settings. When moved Kwin crashes Expected Results: Display widget settings, able to move the widget when dragging the handle. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158 --- Comment #8 from Jens Reuterberg <ohy...@gmail.com> --- (In reply to Jens Reuterberg from comment #7) > So after digging around I found that MX theme DO have a colour file, so it > sets its own colours. Now in the colour file you can edit [colors:window] > and ForegroundNormal to change colour theme of the taskmanager. With that > parts of the theme change as well like the clock - but that you can change > back by defining it in [colors:view] Sry that doesnt set clock colour so I guess you have to use the same for all those. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158 --- Comment #7 from Jens Reuterberg <ohy...@gmail.com> --- So after digging around I found that MX theme DO have a colour file, so it sets its own colours. Now in the colour file you can edit [colors:window] and ForegroundNormal to change colour theme of the taskmanager. With that parts of the theme change as well like the clock - but that you can change back by defining it in [colors:view] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158
--- Comment #6 from Jens Reuterberg <ohy...@gmail.com> ---
> Even if the choice to follow the text color was made by MX Themes creator I
> don't want to be dependent on it. I want to be able to download a theme from
> kde-look and be able to modify to my preference.
Chances are this will not happen though. There are plans for a theme creator
but this is currently on ice as plans to ensure Plasma 5.8 as an LTS are
underfoot - and stability/polish, instead of features, are more relevant to
work on. Such a thing would be something packaged within the Plasma-sdk package
and allow for an easier way to sort SVG's etc to ensure simplicity (sort of
like Theme Explorer in the Plasma-sdk package which I implore you to check out)
Essentially if you make a theme which says "Make all backgrounds in widgets
bright pink", someone downloads your theme and use it - its very tricky for us
to "fix problem with all this bright pink" except suggest that that person
contact the theme creator.
> This is not the same as set color for task manager text independent from
> theme, widget color or whatever. What if I change this theme so that it
> doesn't follow the color of text set by color theme. What color would task
> manager follow then and why it is not clearly explained in techbase
> guidelines?
It follows the Window theme colour. Edit the Window Text Colour in Colour
settings. This will affect ALL text in the window theme though so the solution
isn't optimal.
> What if I want to use other themes that are made the same? Well, that's
> hypothetical question, I have not checked every theme.
Then you wont be able to see the text as well as you would prefer.
> I don't understand what you mean by elegant solution.
A way where the solution for a fringe issue isn't impeding more common use
cases. A solution where simplicity is part of it. If you can't marry these two
into a solution, the solution isn't elegant and as the choice then is "hurt the
majority" or "hurt the minority" the choice is obvious. ("The need of the many
outweigh the need of the few" to quote Mr Spock)
> What I request is options in configuration file and an easy to understand
> description in techbase so that every user can download theme from kde-look
> and adjust it to his/her preference or even mix different elements from
> different themes (for example to mix icons).
That is impossible to do. Theming in Plasma is extremely flexible from a theme
creators POV and the attempt to have a mix-and-match setting was underwhelming
and buggy. Hence it was removed - if a theme editor is created in the future,
hopefully that will work to cover your needs too.
Until then, you have to either
1) edit the theme yourself using for example "Theme Explorer",
2) ask the creator to make a theme with hardcoded text colours for different
elements,
3) change wallpaper,
4) change the colour of the Window Text,
5) Change font to something more readable
6) Swap to a different theme
7) Hang in there and hope for some dev to create a theme editor from scratch
that covers your needs.
Now I am not the end decider, but I was asked in here as someone representing
the VDG - and from our POV unless an elegant solution presents itself, with a
dev attached that can create this solution, there simply isn't anything that
CAN be done except suggest the above fixes to your issue.
As for an easier to understand techbase documentation (or more extensive) and
easier to understand RC files - I can only agree and I wish I could say "a
theme creator coming right up" - but that would just be lying to you. We want
to create a better theming system for the future, sketches exist, but so far
thats as far as we can get. The dev for the taskmanager has stated that he
can't add this new feature to the taskmanager so that avenue is closed too
leaving you with the seven options above to fix your issue.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 364472] show holidays also as text in main view
https://bugs.kde.org/show_bug.cgi?id=364472 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #9 from Jens Reuterberg <ohy...@gmail.com> --- What we need is better communication to theme creators that certain changes are happening and they need to add bits to their themes like in this case a tiny marker with the correct naming. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #4 from Jens Reuterberg <ohy...@gmail.com> --- The text colour should always (or per default) follow the colour theme in Breeze and themes that want this. Since there already exists an option in desktop theme to follow or NOT follow the colour of text set by colour theme, this is a non issue. (Change theme to Oxygen, change to some coloured text for the colour theme and observe that the theme does NOT change colour of text). So the choice to follow the text colour was made by MX Themes creator. In the above screenshot I notice the text in the taskmanager is far more readable than the icons and clock text in the chosen colour theme. To be honest testing it on my own using Gimp to change colours of text I notice that "white" (or #FCFCFC) is probably the best option there and I am slightly curious to know what colour you think would fit better and be more readable? Trying Magenta for example just hides it. My suggestion for fix would be to 1) edit the theme and hardcode the colour of the widget text. 2) change colour of "Window Text" slightly to better fit your needs 3) Change the font used for Taskmanager to something bigger and bolder to make it more readable no matter what colour 4) Change wallpaper 5) Change the theme to not allow transparent widgets in certain cases, like the taskmanager. I simply dont see an elegant solution which only goal is, in practice, to fix one broken theme. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364953] Breeze and Breeze Light themes are the same but listed twice
https://bugs.kde.org/show_bug.cgi?id=364953 --- Comment #4 from Jens Reuterberg <ohy...@gmail.com> --- Created attachment 99798 --> https://bugs.kde.org/attachment.cgi?id=99798=edit example for new Breeze multicolour image -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364953] Breeze and Breeze Light themes are the same but listed twice
https://bugs.kde.org/show_bug.cgi?id=364953 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #3 from Jens Reuterberg <ohy...@gmail.com> --- "Breeze Light", "Breeze Dark" and "Breeze" should be the naming. As for image to represent each differently I think it wont be that difficult - we could add the 5.4 wallpaper or something in the background instead of just light grey colour to represent "any colour you like"? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364931] Regression: Status icon for "not available" (presence) seems to be lacking
https://bugs.kde.org/show_bug.cgi?id=364931 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #2 from Jens Reuterberg <ohy...@gmail.com> --- Worst possible answer: "it works here" ... can you check if the icon is present at all and the issue is somewhere on that end? Just install cuttlefish (its in the plasma-sdk bundle) and search for "user-away-extended" or go to /usr/share/icons/status and check through all the variable sizes? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363206] either install all of oxygen or nothing
https://bugs.kde.org/show_bug.cgi?id=363206 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #1 from Jens Reuterberg <ohy...@gmail.com> --- Nothing then. The main issue here, which I was drawn upon when talking to one of the neon users is that there is no safe way to install bundles (like "everything for complete Oxygen" or "Every addon for Application X to ensure its usability"), but with Oxygen installing it after the fact isn't a big issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359127] Desktop theme KCM 'details' and editing tab no longer present/functional
https://bugs.kde.org/show_bug.cgi?id=359127 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #29 from Jens Reuterberg <ohy...@gmail.com> --- > Why not just give a little love to that feature rather then removing it? It > was very useful! This was one of the biggest features I loved about kde, I > could customize it in the inside (how it works) and outside (how it looks). > Now it's like the half of it was gone. My feeling is, we're going in the > direction of gnome. What is the point of KDE existing if not being extremely > customable and a complete opposite to gnome philosophy? People love KDE for > it and now KDE seems to loose its identity. I'm sad because of that. It simply is one of math - we have a very very limited amount of devs, very few people from the community helping out meaning that even smaller issues becomes things that soak up time for everyone. The theme editor didn't work well enough to be included with a good conscience and currently the best method is one where you use the Plasma-SDK package to check, blend and test themes (the Theme Explorer specifically) - granted I too want a better situation where perhaps we could have a "theme creator" as an application or something. But that has to be a future choice and one based on whether there are people enough to do it. Having a Plasma desktop starting, working as expected, systemtray etc is more relevant than the theme editor which is harsh but the truth. Love sadly is no match against "manpower", "time" and "developer fatigue" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360733] screen scaling window does not let you scale below 100%
https://bugs.kde.org/show_bug.cgi?id=360733 Jens Reuterberg <ohy...@gmail.com> changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #2 from Jens Reuterberg <ohy...@gmail.com> --- I think this is mostly visual in nature since it's (reading from your reddit post OP) more about making the widget parts smaller. You should in my opinion pick a slimmer widget theme (check out the different Qtcurve themes available) and make your fonts smaller. Enforcing a downwards resize seems like a hassle in comparison to the gain when workarounds are available. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 294778] unlock screen should show system name
https://bugs.kde.org/show_bug.cgi?id=294778 --- Comment #1 from Jens Reuterberg <ohy...@gmail.com> --- My suggestion would be to switch wallpapers in the lockscreen - on the one hand there are ways to include a name from a design perspective without any issue to the Breeze theme but at the same time the same thing can be acquired by the user changing wallpapers on one of his/her identical laptops. (You can even add your computer Name to the lockscreen wallpaper in gimp and use that?) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 351393] support Ctrl+W in password field
https://bugs.kde.org/show_bug.cgi?id=351393 --- Comment #1 from Jens Reuterberg <ohy...@gmail.com> --- I know it would be cool to add more shortcut methods for lockscreen but in this very specific use case I think that its one of those "it will cause way more problems implementing than its worth" - its easier to force you to retrain muscle memory/hold in backspace only than adding the choice to set shortcuts for off-key lockscreen actions. At least for the time being. -- You are receiving this mail because: You are watching all bug changes.
