from http://bugs.musicbrainz.org/ticket/2663

When Picard is off doing things with several thousand files (yeah, I know) it's quite difficult to know whether you can click in the UI or have to wait. A "busy" cursor would help a lot while loading files from drag+drop and sending PUIDS etc..

I was thinking that you could fit two messages on the bottom of the window where you are currently writing (and immediately over-writing) information now. If you had two lines in a scrolling window, the user could easily see what just happened and what it was doing before that. This gives the user a 2nd chance to read a message before it's gone and the scrolling naturally indicates that PicardQt is busily doing his duty.

More importantly, if PicardQt locks up, it's easier to see exactly what the last couple of things were that caused the problem. That and the log can help narrow down the problems faster.