New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changed: background file manager operations #1541
Conversation
this depends on pr #1530 |
nice |
better split now and no longer depends on #1530 |
Looks good to me. A few functions could be const (You asked for it by changing one that wasn't related...) |
hah, as if i'd ever do such a thing ;) put it in the correct context now + made the new functions const. |
no other concerns? |
If you are interested in a user opinion: I would like it even more if it would copy or move files one after another with any kind of queue and not parallel. |
it's sorta what it does. it does two user-initiated operations in parallel. an operation can be copying n files or n dirs or whatever. |
Oh, looks like I was not precise enough - sorry. |
i got you. if, however, you mark file a and file b and hit copy, they will be copied in sequence. doing it all in sequence is trivial, that's just removing the 2 thread slots. but imo this is better. |
changed: background file manager operations
As in the topic. I could probably split this a bit if you insist, but it got so damm entangled..