INTERACT FORUM

More => Old Versions => JRiver Media Center 19 for Mac => Topic started by: Fred1 on July 07, 2014, 01:34:19 pm

Title: GUI is dead when copying/moving many files
Post by: Fred1 on July 07, 2014, 01:34:19 pm
The GUI isn't working any more if you copy a lot of files.
It would be fine if  there were a progress bar or something like that.
Title: Re: GUI is dead when copying/moving many files
Post by: bplexico on July 07, 2014, 07:34:22 pm
When you say "copy a lot of files", what do you mean? While importing a large number of albums (files) into the JRiver library?

What hardware are you running JRiver on? And how many files are copying?

Barr
Title: Re: GUI is dead when copying/moving many files
Post by: glynor on July 07, 2014, 10:31:57 pm
When I copy a large number of files (I just tried 1.66GB in one go, along with several smaller batches), via drag-and-drop into the Finder, MC remains responsive once the copy begins.

However, I did have trouble with responsiveness (and even one MC/Finder lockup that lasted long enough for me to force quit both), when actually performing the drag drop.  It seems to hang on the odd "finder zooming" animation thing it does.  Or maybe the odd auto-window-placement rearranging thing that Mavericks does when you drag drop with multiple monitors?

Dunno.  Once I got past that, though, it worked without issue, and MC's GUI was responsive, and I could play stuff and browse wherever.

That's drag-drop.  Not sure how you're doing it, or what you're doing, because you didn't explain.
Title: Re: GUI is dead when copying/moving many files
Post by: Fred1 on July 07, 2014, 11:53:28 pm
That's what i'm doing:
I copy files to another Mac over WiFi.

(http://foto.arcor-online.net/palb/alben/08/1895808/6431623731623930.jpg)

After clicking Ok, MC doesn't respond any more.
The number of files is about 7,000.

If i CMD-TAB to another application, there is no way back to MC until the copy operations have finished.
The copies themselves do work ok.
Only the GUI is dead until copying is done, then it is responsive again.

In C# (Windows) a call to DoEvents() in the right place would solve such a problem.