[frameworks-kiconthemes] [Bug 452341] When an icon is not found from its specified absolute path, look for it in the active icon theme before giving up
https://bugs.kde.org/show_bug.cgi?id=452341 --- Comment #6 from Frank Souza --- "would never return a match." Well, this is a concern for icon theme designers. On the team breeze side, they don't have to worry, the most that can happen is what already happens, the icon can't be found, and that's where the sense of third parties contributing their themes comes in. The meaning of using "_foo_bar_icon" instead of "icon", as I said, is the context. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 452341] When an icon is not found from its specified absolute path, look for it in the active icon theme before giving up
https://bugs.kde.org/show_bug.cgi?id=452341 --- Comment #4 from Frank Souza --- The proposal to convert "/foo/bar/icon.svg" to "_foo_bar_icon" and not just "icon" is, as you may have noticed, the context. eg /my/app/icon/path/logo.svg will be converted to a very generic icon name "logo". "_my_app_icon_path_logo" looks more specific, and can be covered respecting the dev's intentions -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 452341] Feature request: use relative paths for icons not found in absolute paths
https://bugs.kde.org/show_bug.cgi?id=452341 --- Comment #2 from Frank Souza --- (In reply to Nate Graham from comment #1) > Is there a specific circumstance in which would would expect a file looked > for at /usr/share/icons/Humanity/devices/48/printer.svg would instead be > ./_usr_share_icons_Humanity_devices_48_printer.svg? This seems oddly > specific. When I say "relative", I'm saying relative to the icon theme, not relative to current working directory (./). The proposal is: if an icon is not found in the absolute path specified by the program (in my example, it is not a program, just a .desktop file), the process responsible for interpreting the path should try to use an icon of the current theme as a fallback (before using the mimetype "empty file" icon). I don't know how ubuntu software center is going since I use manjaro, but a few years ago this was the way USC assigned icons to its programs inside of it, if it was not found within the manifest (or something like that), it uses an icon in this format, being affected by the current icon theme. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 452341] New: Feature request: use relative paths for icons not found in absolute paths
https://bugs.kde.org/show_bug.cgi?id=452341 Bug ID: 452341 Summary: Feature request: use relative paths for icons not found in absolute paths Product: frameworks-kiconthemes Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: franksouza...@protonmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I don't think there's anyone who hasn't come across .desktop files with no icon set, caused by absolute paths not being found. The idea is to allow icon themes to override. Suggestion: in icon search process, convert absolute paths into relative paths by replacing slashes with some non directory related. Eg: /usr/share/icons/Humanity/devices/48/printer.svg to _usr_share_icons_Humanity_devices_48_printer.svg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389990] Some icons are badly rendered on system tray
https://bugs.kde.org/show_bug.cgi?id=389990 --- Comment #5 from Frank Souza <franksouza...@gmail.com> --- As suggested in the SSR bug report, sni-qt made this work as it should, but not for programs running in root mode, such as radeon-profile. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389990] Some icons are badly rendered on system tray
https://bugs.kde.org/show_bug.cgi?id=389990 --- Comment #4 from Frank Souza <franksouza...@gmail.com> --- Thank you for your time! Bug reported: https://github.com/MaartenBaert/ssr/issues/624 >From a superficial look, do you think this is a complex thing to fix? I mean, would I be correct in my suspicion of it be using re-scale unnecessarily (when the graphic already has the final rendering dimensions)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389990] Some icons are badly rendered on system tray
https://bugs.kde.org/show_bug.cgi?id=389990 --- Comment #2 from Frank Souza <franksouza...@gmail.com> --- Yes, this one uses xembed, but I do not think a proper solution ask all developers for these programs (including some abandoned but still heavily used). Why not fill out a bug report for the xembed team and make them render things as they should? These icons are displayed correctly in other environments, such as xfce, cinamon, gnome-shell. -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 389990] New: Some icons are badly rendered on system tray
https://bugs.kde.org/show_bug.cgi?id=389990 Bug ID: 389990 Summary: Some icons are badly rendered on system tray Product: ksystraycmd Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: franksouza...@gmail.com Target Milestone: --- Sorry if I missed the related product. I already noticed this in earlier versions of KDE. There is a certain loss of quality in some icons when rendered on system tray regardless its size, as you can see here: https://i.imgur.com/Zhm8H3p.png. Look's like some kind of antialising or scaling is being applied. That is the icon of Simple Screen Recorder clearly modified just for tests. In this example, the graphic is rendered with 22 x 22px, the icon has exactly the same dimensions and also, as you can see, has only squares, so no antialiasing should be visible. Sorry for the bad english -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378419] "Locate current document in project" button in project view not working
https://bugs.kde.org/show_bug.cgi?id=378419 --- Comment #9 from Frank Souza <franksouza...@gmail.com> --- Taking into account the concept of symbolic link, this is something that must be fixed since this break its purpose -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378419] "Locate current document in project" button in project view not working
https://bugs.kde.org/show_bug.cgi?id=378419 --- Comment #6 from Frank Souza <franksouza...@gmail.com> --- I've figure it out: symbolic links. The major part of my php files are sym links from a base project. Now I don't know if this a bug or expected. That's why I'll not mark as resolved until someone confirm. Thanks everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378419] "Locate current document in project" button in project view not working
https://bugs.kde.org/show_bug.cgi?id=378419 Frank Souza <franksouza...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|RESOLVED|UNCONFIRMED --- Comment #4 from Frank Souza <franksouza...@gmail.com> --- Sorry for the lack of information. I did some more tests and only then realized that this problem occurs only in .php files, for other files this seems to work. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378419] New: "Locate current document in project" button in project view not working
https://bugs.kde.org/show_bug.cgi?id=378419 Bug ID: 378419 Summary: "Locate current document in project" button in project view not working Product: kdevelop Version: 5.1.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: franksouza...@gmail.com Target Milestone: --- I can't remember wich version before the last update (5.1.0) it was working, but for sure the 4.x.x I had used this a lot, becomes essential to me, now I'm lost within millions files list in the project view. :/ -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 143527] konqueror filemanager cannot produce relative symlinks
https://bugs.kde.org/show_bug.cgi?id=143527 Frank Souza <franksouza...@gmail.com> changed: What|Removed |Added CC||franksouza...@gmail.com --- Comment #10 from Frank Souza <franksouza...@gmail.com> --- The bug persists: Arch Linux 64 dolphin 16.08.1 KDE Frameworks 5.26.0 Qt 5.7.0 (compiled with 5.7.0) xcb windows system -- You are receiving this mail because: You are watching all bug changes.
