QUOTE(pirlouy @ Mar 29 2007, 16:48)

When I click on image to download preview, it often freezes, I have to kill process...
Is it a known bug (fixed in next build) ? (I use the latest version)
This is not a known bug, and I couldn't reproduce it. Please try the new version 0.2 I just published, and see if it helps.
QUOTE(dub_doctor @ Apr 1 2007, 02:30)

The "stop all" button also takes a bit of time to kick in, freezing the program for a while in the process. If you wait a bit it comes back, but you need a bit of patience.
When stopping, it does generally need to complete the result it is currently adding before stopping a source. When using Stop All, there can be a lot of sources to wait for, but it still shouldn't freeze the program while it is waiting. I'll see if I can do anything about that.
QUOTE(dub_doctor)

It would be nice to be able to just search for a particular source, and then add a new source to the search without the program doing the entire search all over again. eg. do the initial search without GoogleImage (since that can take quite a while), then choose to add GoogleImage to the search if you need more results.
Interesting. I like the idea, so if I can think of a good way of doing it, I might put that in.
QUOTE(dub_doctor)

Something like the "Save Toolbar" from the previous version would also be useful, so that you can eg. save cover_front.jpg, cover_back.jpg, artist.jpg, cd.jpg or whatever custom pics you like without having to enter it manually every time.
The "Save Images To" box has a drop down history list, so if you have used that to define a pattern including _front or _back or whatever previously, you can just pick it from the list. The filename to save to will update in the results panels to reflect the change.
QUOTE(wraithdu @ Apr 1 2007, 04:50)

Nice job! All the new features are great and work wonderfully.
However...as much as I love your program, I HATE .NET 3!!!! This framework runs like molases on all my computers, crashes frequently, and uses more RAM than any program has a right to (hundreds of megs, at least). Microsoft needs to address these resource issues ASAP, cause it SUCKS!
I can't argue with the runs like molasses. The thing is big and fat and slow. When I started working with it, I was hoping that WPF performance would be improved by release, but apparently not.
I wouldn't worry about the RAM, though, the way .net works (due to the garbage collection system) is to gobble up as much RAM as it can to improve performance, but if the system starts to run out and other things require it, it will release as much as it needs to.
I haven't noticed frequent crashes with it at all, though - that might indicate some problem that could be fixed, if you wanted to put in the time and effort.
Other than that, I can only apologise, but a large part of the reason for doing this rewrite was to gain experience in writing software in WPF which, for better or worse, is likely to become something I will need to know.