Right now I'm rescanning my track collection on my laptop, and I expected it to
be a short operation, but it's taking forever. I'm guessing it's because I
moved a large part of my track collection to a different partition on my hard
drive, even though the path remained the same. The issue is that QDirIterator
doesn't present the tracks in any particular order; it'll be dictated by how
they happened to be stored in the underlying filesystem. When I moved the
track collection, that permuted the files in each directory.
The issue is that the directory-hash calculation isn't order-independent; it
calculates the directory hash by appending all the filenames to one string. If
we changed it to calculate the hash of each filename individually, and XORed
those together, then it would be order-independent, and shouldn't detect less
changes than the previous method.
Thoughts?
Steven Boswell
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
