[gwenview] [Bug 443168] Add a setting to not follow sorting as in Dolphin when Gwenview started by image click

2025-03-10 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=443168 Quincy changed: What|Removed |Added CC||bbc.qui...@gmx.de --- Comment #33 from Quincy

[digikam] [Bug 431788] Add option available to not resample images in viewer

2024-11-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=431788 --- Comment #6 from Quincy --- Downloaded digiKam-8.5.0-20241102T170111-Qt6-x86-64.appimage for testing - works exactly as expected! For "artistic" photos the scaler is fine and does what it should do, for the purposes outlined here it i

[digikam] [Bug 431788] Add option available to not resample images in viewer

2024-10-28 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=431788 --- Comment #2 from Quincy --- Created attachment 175310 --> https://bugs.kde.org/attachment.cgi?id=175310&action=edit Comparison gwenview vs. digikam Unfortunately I was never notified of your answer via email, therefore I'm a bit

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-06-01 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #14 from Quincy --- I was always referring to copying files outside of digiKam, but I will test with digiKam 7.3 on both systems when its out or with a current appimage build. Many thanks so far! -- You are receiving this mail because

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-06-01 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 Quincy changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-06-01 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #11 from Quincy --- Created attachment 138922 --> https://bugs.kde.org/attachment.cgi?id=138922&action=edit New test file with sufficient size and zipped -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-06-01 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 Quincy changed: What|Removed |Added Attachment #138908|0 |1 is obsolete

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-05-31 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #3 from Quincy --- Created attachment 138908 --> https://bugs.kde.org/attachment.cgi?id=138908&action=edit Test file I created a simple TIFF file which has: Creation‎: Montag, ‎31. ‎Mai ‎2021, ‏‎16:04:20 ‎Modification: Montag, ‎3

[digikam] [Bug 437897] Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-05-31 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 --- Comment #2 from Quincy --- Rotation took place in the main window/thumbnail view (either within the preview with the icons in the upper left corner or via the menu "Item -> Rotate"). This updates the existing image in place. For re

[digikam] [Bug 437897] New: Windows timestamp to metadata extraction for TIFFs changes when modifying files

2021-05-31 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=437897 Bug ID: 437897 Summary: Windows timestamp to metadata extraction for TIFFs changes when modifying files Product: digikam Version: 7.2.0 Platform: Microsoft Windows

[digikam] [Bug 436571] Tooltips for images don't show tags containing "<" correctly

2021-05-04 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=436571 --- Comment #6 from Quincy --- Thanks Maik for the quick fix! @Gilles: I usually do not taint the image files with anything, so I had to find again how to reactivate that behavior temporarily. BTW on that: The Menu entry to write metadata into files

[digikam] [Bug 436571] Tooltips for images don't show tags containing "<" correctly

2021-05-04 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=436571 --- Comment #3 from Quincy --- @Gilles: It is not metadata saved within the image, but a tag assigned via digiKam (database only). I think Maik is right, as "Test Test2" completely removes the part between the angle brackets. -- You are

[digikam] [Bug 436571] New: Tooltips for images don't show tags containing "<" correctly

2021-05-04 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=436571 Bug ID: 436571 Summary: Tooltips for images don't show tags containing "<" correctly Product: digikam Version: 7.2.0 Platform: Microsoft Windows OS: Microsoft Wind

[digikam] [Bug 434275] Row height determined by number of tags even if they are not visible

2021-03-11 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=434275 --- Comment #4 from Quincy --- With digiKam-7.2.0-20210311T200524-Win64.exe the issue is solved. Very nice and fast work, very much appreciated :-) -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 434275] Row height determined by number of tags even if they are not visible

2021-03-11 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=434275 --- Comment #1 from Quincy --- Just found out because it was a quite long list in my case and further testing: There is some update problem, as I finally could manage to display all entries in a "one-line" row after switching back an

[digikam] [Bug 434275] New: Row height determined by number of tags even if they are not visible

2021-03-11 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=434275 Bug ID: 434275 Summary: Row height determined by number of tags even if they are not visible Product: digikam Version: 7.1.0 Platform: Microsoft Windows OS: Micros

[digikam] [Bug 431788] New: Make option available to not resample images in viewer

2021-01-18 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=431788 Bug ID: 431788 Summary: Make option available to not resample images in viewer Product: digikam Version: 7.1.0 Platform: unspecified OS: Unspecified Status: REPORTED

[digikam] [Bug 430147] Search and escaping of database wildcard characters in filenames

2020-12-09 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=430147 --- Comment #4 from Quincy --- Thanks for the quick fix. So the wildcards "_" and "%" will still be usable and have to be escaped if one needs to use them as literal? Could one please update the documentation accordingly as wild

[digikam] [Bug 430147] New: Search and escaping of database wildcard characters in filenames

2020-12-08 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=430147 Bug ID: 430147 Summary: Search and escaping of database wildcard characters in filenames Product: digikam Version: 7.1.0 Platform: Microsoft Windows OS: Microsoft

[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor when Gwenview is already maximized

2018-06-22 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=372417 --- Comment #11 from Quincy --- I was just about to test with the new user, but had to wait for other stuff to get finished before restarting with a different user. It is kind of weird, that Daniel and my behavior fulfilled this rather complicated

[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor when Gwenview is already maximized

2018-06-20 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=372417 --- Comment #8 from Quincy --- For me it is still valid as described, even given that I now have newer package versions installed than Daniel: Gwenview 17.12.3 / KF 5.46.0 / Qt 5.9.4 / kwin 5.12.5 but on Gentoo Linux -- You are receiving this mail

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2018-01-04 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #15 from Quincy --- Current AppImage Version (including your fixes) happily upgrade DB Version 8->9. Upgrade of a restored V7 DB to 8 (and then 9) first fails with: digikam.dbengine: Failure executing query: Error messages: &quo

[digikam] [Bug 388351] Use AppImage SDK version 10 instead 6 to be compatible with FireJail

2018-01-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=388351 --- Comment #5 from Quincy --- Works, thanks! -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #11 from Quincy --- I'm using MySQL on the very same computer as digikam. This is "local", but not internal to digikam as the MySQL server is running separately (for web development and other stuff, too). Because it is th

[digikam] [Bug 388351] New: AppImage is not compatible with firejail

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=388351 Bug ID: 388351 Summary: AppImage is not compatible with firejail Product: digikam Version: 5.8.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishl

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #9 from Quincy --- I'n not in a hurry given the raised points. A new image with localhost/socket support does not change things. @Maik: I already went for a more manual (and cumbersome) step-by-step approach to migrate V7->8: - d

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #7 from Quincy --- As Maik said the new version does not solve/change this bug, so I am wondering why Gilles has posted to try the appimage to especially this bug. At least I could test the upgrade from V8 to 9 with my manually "mig

[digikam] [Bug 388345] AppImage MySQL connection issues

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=388345 --- Comment #4 from Quincy --- Thanks for the quick response! Using 127.0.0.1 indeed solves the problem, but just because it does not connect using the socket at all. If you have a non-networking server (MySQL: "skip-networking") this doe

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-29 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #5 from Quincy --- Wanted to check the new update capabilities, but was unfortunately stopped by bug #388345. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 388345] New: AppImage MySQL connection issues

2017-12-29 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=388345 Bug ID: 388345 Summary: AppImage MySQL connection issues Product: digikam Version: 5.8.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal

[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor when Gwenview is already maximized

2017-12-02 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=372417 --- Comment #5 from Quincy --- Now I am on Gwenview 17.04.3 / KF 5.37 / Qt 5.7.1 but the problem still persists. I am using Plasma/kwin-5.10.5 and gwenview is opened via double clicking a file in dolphin on the first screen (resolution 1440x900). This

[digikam] [Bug 342427] Timing issues when large GPX file is loaded and option "Show tracks on Map" is used with GoogleMaps

2017-09-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=342427 --- Comment #8 from Quincy --- Ahh cool, never seen that. Regarding the bug: Behaves the same as with my "old" 5.5.0 version. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 342427] Timing issues when large GPX file is loaded and option "Show tracks on Map" is used

2017-09-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=342427 --- Comment #6 from Quincy --- 5.7.0 is unfortunately not yet available in my distribution. I used standard GPS correlation not the reverse one (which I never used as it seems to work on tags vs. location names). For loading there are no options at all

[digikam] [Bug 342427] Timing issues when large GPX file is loaded and option "Show tracks on Map" is used

2017-09-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=342427 --- Comment #4 from Quincy --- On the very same hardware as of my initial report, but now with DigiKam 5.5.0 it now takes 11s to load a file with 185000 waypoints, and 26s to re-enable. For a smaller file (7 waypoints) it takes 4s to load and 5 to

[digikam] [Bug 384306] New: Option to center map on selected track

2017-09-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=384306 Bug ID: 384306 Summary: Option to center map on selected track Product: digikam Version: 5.5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity:

[digikam] [Bug 342352] Relocate "Show tracks on map" option on GUI

2017-09-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=342352 Quincy changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution

[digikam] [Bug 379987] New: UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-05-18 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 Bug ID: 379987 Summary: UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific) Product: digikam Version: 5.5.0 Platform: Gentoo Packages OS: Linux

[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor

2017-03-23 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=372417 --- Comment #3 from Quincy --- At least I found a workaround: When Gwenview window is not maximized on that screen going to fullscreen mode works. It only jumps to the other screen if it is already maximized. Additionally I am not sure if this is

[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor

2016-12-03 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=372417 Quincy changed: What|Removed |Added CC||bbc.qui...@gmx.de --- Comment #1 from Quincy --- I