https://bugs.kde.org/show_bug.cgi?id=369051
--- Comment #3 from Mario Frank ---
Hey Gilles,
those are good news. I agree with you concerning the improved usability by
ordering the, as I understand, list of results in the left pane where the
reference image and count of similar images is shown
https://bugs.kde.org/show_bug.cgi?id=372217
Bug ID: 372217
Summary: The results of the Duplicates are currently sorted by
the image id and sortable by name and count if
similars. But it should be sortable by the similarity
https://bugs.kde.org/show_bug.cgi?id=372217
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=372217
--- Comment #1 from Mario Frank ---
Created attachment 102121
--> https://bugs.kde.org/attachment.cgi?id=102121&action=edit
The second patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=261417
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=369051
--- Comment #8 from Mario Frank ---
Hey Gilles,
Many thanks for the judgement about the quality of my patches.
I will try to fix what I can. Some of the "bugs" do not seem to be hard to fix.
Some other could be more complex.
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=369051
--- Comment #9 from Mario Frank ---
By the way: the CCMAIL is incorrect. The correct one is
mario.fr...@uni-potsdam.de. If the dot should be a problem, just use
mafr...@uni-potsdam.de.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #4 from Mario Frank ---
Created attachment 102157
--> https://bugs.kde.org/attachment.cgi?id=102157&action=edit
Patch for the bug.
Tested this patch. Seems to work quite well. Please review it.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #6 from Mario Frank ---
Hey, I just tested again. Deleting multiple pictures (selection) at the same
time
does not work properly, too. The counter is only decremented by 1, not by the
count of deleted images. Seems that the signal
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #8 from Mario Frank ---
Okay. In fact I fired a signal to the AlbumManager and then to the
FindDuplicatesView. I will take a look at the problem more closely.
Is there an overview concerning wirings? And is there an UI definition that can
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #11 from Mario Frank ---
I do not know how the developers opinions are. But I think what you see is part
of the problem described in bug 372217 . I already adressed the lexicographical
ordering of the simmilarity. I will provide a patch for
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #13 from Mario Frank ---
Hey Gilles,
by the wiring (of components), I mean the connection of signals to slots. The
lack on information about which class is the correct view in which situation
makes it complicated for me to get find out
https://bugs.kde.org/show_bug.cgi?id=372442
Bug ID: 372442
Summary: Ordering of duplicates search by the result count is
done lexicographically.
Product: digikam
Version: 5.3.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=372442
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #15 from Mario Frank ---
Hey Gilles,
there are obviously 3 ways to delete an image:
1 pressing the delete key
2 klicking the right mouse button on the image and move to trash
3 moving to trash with the main menu (entry->move to trash)
https://bugs.kde.org/show_bug.cgi?id=302923
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=274360
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=302923
--- Comment #3 from Mario Frank ---
Hey Wolfgang (if I may),
I fear that my comment induced a quite too fatalistic view. Thus, I want to
make that more precise. Depending on the way of implementation, the effort may
be smaller or higher. Communicating
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #18 from Mario Frank ---
Hey,
I found all that spots when I extended the duplicates search to the interval
variant. And I did see the contextmenuhelper, too.
And I traced the signal-slot-connections. The image preview view signals the
https://bugs.kde.org/show_bug.cgi?id=369051
--- Comment #11 from Mario Frank ---
I agree, Wolfgang. Similarity range is a better description here.
Moreover, I just realised that it is not possible to set a range in the
maintainance dialog. I will open a new file for both parts and submit a patch
https://bugs.kde.org/show_bug.cgi?id=372583
Bug ID: 372583
Summary: The Similarity in DuplicatesSearch and FuzzySearch
should be renamed to Similarity range [patch]
Product: digikam
Version: 5.4.0
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=372584
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=372584
Bug ID: 372584
Summary: It is not possible to give a similarity range for
duplicates search in maintenance dialog [patch]
Product: digikam
Version: 5.4.0
Platform: Compiled Source
https://bugs.kde.org/show_bug.cgi?id=372583
Mario Frank changed:
What|Removed |Added
Platform|Other |Compiled Sources
CC
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #20 from Mario Frank ---
(In reply to caulier.gilles from comment #19)
>
> Well, it's simple. If one image can be present in more than one SAlbum, all
> relevant SAlbum must be updated through DuplicatesFinder tool.
>
&
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #21 from Mario Frank ---
(In reply to Mario Frank from comment #20)
> (In reply to caulier.gilles from comment #19)
> >
> > Well, it's simple. If one image can be present in more than one SAlbum, all
> > relev
https://bugs.kde.org/show_bug.cgi?id=261417
--- Comment #22 from Mario Frank ---
Okay, I looked for other ways to signal the AlbumManager about the deleted
images and I did not find performant ways to do this in another way.
Thus, I will upload the patch. Here is the commit message:
"[
https://bugs.kde.org/show_bug.cgi?id=261417
Mario Frank changed:
What|Removed |Added
Attachment #102157|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=372781
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=372781
Bug ID: 372781
Summary: The recent similarity range is not saved which may
lead to odd results.
Product: digikam
Version: 5.4.0
Platform: Compiled Sources
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=372781
--- Comment #2 from Mario Frank ---
(In reply to caulier.gilles from comment #1)
> If i'm not too wrong, the similarity threshold must be saved in SAlbum in
> database, as property. We need to do the same for max threshold typically...
https://bugs.kde.org/show_bug.cgi?id=372781
--- Comment #3 from Mario Frank ---
Created attachment 102389
--> https://bugs.kde.org/attachment.cgi?id=102389&action=edit
The proposed patch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372781
--- Comment #5 from Mario Frank ---
(In reply to caulier.gilles from comment #4)
> >I do not think that accessing the digikamrc from different classes
> >(DublicatesFinder, FindDuplicatesView and MaintenanceMgr) is a really good
> >
https://bugs.kde.org/show_bug.cgi?id=372781
Mario Frank changed:
What|Removed |Added
Attachment #102389|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=372872
Bug ID: 372872
Summary: Possible Null-Pointer dereference in AlbumManager
[patch]
Product: digikam
Version: 5.4.0
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=372872
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=368734
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=373100
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=373100
--- Comment #2 from Mario Frank ---
(In reply to Kristian Karl from comment #1)
> I noticed afterwards that step 8) is not necessary.
Hi,
I stumbled over this one yesterday, too. This dysfunction was not present
before.
Will trace it today. The ot
https://bugs.kde.org/show_bug.cgi?id=373100
--- Comment #4 from Mario Frank ---
(In reply to Simon from comment #3)
> Hi Frank,
>
> Why do you want to rescan on a delete? This is extremely time consuming when
> the duplicate search is done over a big amount of pictures. The expec
https://bugs.kde.org/show_bug.cgi?id=373100
Mario Frank changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=373100
--- Comment #6 from Mario Frank ---
Okay, I found the evil guy. Some small bug. Will fix that today.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373100
Mario Frank changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=320666
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=416462
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=416462
--- Comment #9 from Mario Frank ---
(In reply to caulier.gilles from comment #7)
> Hi Mario and happy new year,
>
> Well, i don't have a best idea, excepted the fact to use a deep learning
> method. Typically, We have a bug en
https://bugs.kde.org/show_bug.cgi?id=416462
--- Comment #10 from Mario Frank ---
(In reply to Daniel from comment #8)
> Hi all,
>
> so I think they are 2 different cases here (both could theoretically be
> solved by the same solution, but probably shouldn't), and I don'
https://bugs.kde.org/show_bug.cgi?id=426116
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=392025
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=390136
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=375375
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=375375
--- Comment #8 from Mario Frank ---
Git commit dee3647b19a3e8c44292da19821fa0221400bb04 by Mario Frank.
Committed on 24/01/2017 at 14:37.
Pushed by mfrank into branch 'master'.
Made the detect and recognise pipeline for face detection and r
https://bugs.kde.org/show_bug.cgi?id=375375
--- Comment #9 from Mario Frank ---
Hey, had some time to search for the bugs yesterday evening.
The option detect and recognise should work now. There was a bug in fact.
I introduced a workaround until we can take care of the faces management in
https://bugs.kde.org/show_bug.cgi?id=320666
--- Comment #50 from Mario Frank ---
(In reply to Niels from comment #49)
> Great stuff guys! Thank you!
>
> I can't DnD from a browser, but using a staging album as suggested is doable.
Hey Niels,
great to hear you like it.
I restric
https://bugs.kde.org/show_bug.cgi?id=375573
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=375573
--- Comment #3 from Mario Frank ---
Hey Dan,
I will answer inline since there are some things that came me in mind.
(In reply to Dan Dascalescu from comment #2)
> Hey Mario,
>
> Thank you for the explanation. I understand the tradeoff - ac
https://bugs.kde.org/show_bug.cgi?id=374591
Mario Frank changed:
What|Removed |Added
Version|5.4.0 |5.5.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #6 from Mario Frank ---
Created attachment 103766
--> https://bugs.kde.org/attachment.cgi?id=103766&action=edit
This patch introduces garbage collection as maintenance stage and reduces the
amount of generated garbage.
Thi
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #7 from Mario Frank ---
To all who test this patch: Please backup your databases before you test.
Though I made tests without any problems, your databases differ from mine. And
I do not want you to lose data. The core database is only
https://bugs.kde.org/show_bug.cgi?id=323718
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=375703
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=317210
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #37 from
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #8 from Mario Frank ---
Created attachment 103773
--> https://bugs.kde.org/attachment.cgi?id=103773&action=edit
Patch including new files.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375700
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=375700
Mario Frank changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/dig
https://bugs.kde.org/show_bug.cgi?id=375945
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #12 from Mario Frank ---
(In reply to Kusi from comment #9)
> do you have by any chance a branch on a git repo to check out from? I use an
> external mysql server and could test it with that configuration
>
> When you delete a
https://bugs.kde.org/show_bug.cgi?id=375573
Mario Frank changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/dig
https://bugs.kde.org/show_bug.cgi?id=376020
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=375703
--- Comment #10 from Mario Frank ---
(In reply to Maik Qualmann from comment #8)
> I have for a test the workaround code removed.
>
> https://cgit.kde.org/digikam.git/tree/libs/database/item/imagescanner.
> cpp#n393
>
> But th
https://bugs.kde.org/show_bug.cgi?id=375703
--- Comment #11 from Mario Frank ---
I have to correct myself. Moving the group back suddenly destroyed the group
relation... That's odd.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375703
--- Comment #15 from Mario Frank ---
Okay,
I thought about the problems for some time.
I try to resume the expected behaviour:
1) Moving a group of items should preserve the grouping relation on the moved
items (Bug description by Jens) - This works
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #13 from Mario Frank ---
What about the garbage collection branch. When will we merge it to master?
I identified some potential stale data, i.e. table entries that reference a
non-existent image id, in core DB that can also be collected.
I
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #15 from Mario Frank ---
(In reply to caulier.gilles from comment #14)
> Hi Mario,
>
> Well, merge back will be done when you decide. If more time is necessary to
> hack, we can postbone release date for 5.5.0.
>
> In ot
https://bugs.kde.org/show_bug.cgi?id=374591
--- Comment #16 from Mario Frank ---
Merge is done. I will close this file now
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374591
Mario Frank changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/dig
https://bugs.kde.org/show_bug.cgi?id=323718
Mario Frank changed:
What|Removed |Added
Version Fixed In||5.5.0
Resolution
https://bugs.kde.org/show_bug.cgi?id=317210
Mario Frank changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=388981
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=377523
Mario Frank changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=261831
Mario Frank changed:
What|Removed |Added
CC||sven.schicked...@gmail.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=402659
Mario Frank changed:
What|Removed |Added
Version Fixed In||6.0.0
Resolution
https://bugs.kde.org/show_bug.cgi?id=377719
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #20 from
https://bugs.kde.org/show_bug.cgi?id=383326
Bug ID: 383326
Summary: Moving a tag does not update the parent tag correctly
Product: digikam
Version: 5.7.0
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Se
https://bugs.kde.org/show_bug.cgi?id=383326
--- Comment #1 from Mario Frank ---
I got a small MySQL database to work right now and was able to reproduce
the corruption. I even got an error message in the trace:
"
digikam.dbengine: Prepare failed!
digikam.dbengine: Failure executing
https://bugs.kde.org/show_bug.cgi?id=383326
Mario Frank changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=383326
--- Comment #3 from Mario Frank ---
Hey meku,
yes, I saw these errors yesterday, too. Getting rid of the errors is easy but
does not solve the main problem that lft and rgt are not updated properly.
If noone does solve the problem before I do, I will
https://bugs.kde.org/show_bug.cgi?id=395125
Mario Frank changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=394489
Mario Frank changed:
What|Removed |Added
CC||skala.vacla...@seznam.cz
--- Comment #19 from
https://bugs.kde.org/show_bug.cgi?id=395086
Mario Frank changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=394489
Mario Frank changed:
What|Removed |Added
CC||davidlev...@yahoo.com
--- Comment #20 from Mario
https://bugs.kde.org/show_bug.cgi?id=394489
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=353331
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=376359
Mario Frank changed:
What|Removed |Added
CC||mario.fr...@uni-potsdam.de
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=283062
Mario Frank changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/dig
https://bugs.kde.org/show_bug.cgi?id=329353
--- Comment #3 from Mario Frank ---
Git commit 2f8ddd42ef62d7aea9e490cdb05ffcc644810c81 by Mario Frank.
Committed on 22/02/2017 at 15:05.
Pushed by mfrank into branch 'master'.
Merged the current state of the garbage collection branch whic
https://bugs.kde.org/show_bug.cgi?id=216895
Mario Frank changed:
What|Removed |Added
Version Fixed In||5.5.0
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=374225
Mario Frank changed:
What|Removed |Added
Version Fixed In||5.5.0
Resolution
https://bugs.kde.org/show_bug.cgi?id=351658
--- Comment #31 from Mario Frank ---
Git commit 2f8ddd42ef62d7aea9e490cdb05ffcc644810c81 by Mario Frank.
Committed on 22/02/2017 at 15:05.
Pushed by mfrank into branch 'master'.
Merged the current state of the garbage collection branch whic
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #18 from Mario Frank ---
Git commit 2f8ddd42ef62d7aea9e490cdb05ffcc644810c81 by Mario Frank.
Committed on 22/02/2017 at 15:05.
Pushed by mfrank into branch 'master'.
Merged the current state of the garbage collection branch whic
1 - 100 of 244 matches
Mail list logo
