ronso0
ronso0
The report now looks like this  We _could_ calculate **new** missing tracks but I don't think that's worth it.
> It would make sense to print the scan results into the log output at startup, if Mixxx is started in developer mode. The report is always logged, just the...
> I think we have a scanning dialog that pops up when the scan takes longer. There is a risk that mixxx is locked when using the library during scanning....
> How about showing the dialog only if new tracks are found or some are missing in the startup case? Yes, that wold make sense. new tracks, new missing tracks,...
> For my use case it would be also nice to put new tracks in an "Incoming" crate. The "New tracks" feature / crate would make sense. How / when...
I think the report can be optimized. IMO this is sufficient: > Scan took 1181 ms. > >1 new tracks found 0 moved tracks detected 1 tracks are missing 0...
The report dialog now only displays relevant information: new / moved / new missing / rediscovered tracks only if there are any. I'll work on a fixup to show the...
> I'll work on a fixup to show the report dialog during startup only if changes have been detected. done.
This is ready for review again.
Thanks for taking a look! Pre-commit should be happy now. I removed the TODOs you mentioned.