yet another excuse my intervention,
I noticed that ultracopier does not work when you have the "moving files to the trash," in fact re-takes over the interface of the operating system.
In this case, it is possible to integrate ultracopier also for moving files to the trash?
Correct me if I am mistaken, thank you.
moving files to the trash
- alpha_one_x86
- Site Admin
- Posts: 1223
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: moving files to the trash
Hello,
Ultracopier have the copy/move because the explorer send it.
In case of remove, explorer/Windows don't allow it, then I can't.
Cheer,
Ultracopier have the copy/move because the explorer send it.
In case of remove, explorer/Windows don't allow it, then I can't.
Cheer,
Re: moving files to the trash
ok, i understand the reason, thanks for the reply.
Re: moving files to the trash
Interesting! I was also curious regarding this feature 

Hate to write my research paper
- alpha_one_x86
- Site Admin
- Posts: 1223
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: moving files to the trash
Other stuff, without speak of the OS send the move to do to ultracopier:
Each OS have their own method to manage the trash, to solve the name conflict date of remove.
Then in internal it's not really a move (but it's presented as move), then you can't just move to another folder.
Under KDE (you can apply to Windows too), the file is send to database to store the source (to known where recover), the original name and date.
This is done via an API, mean for Ultracopier:
Each OS have their own method to manage the trash, to solve the name conflict date of remove.
Then in internal it's not really a move (but it's presented as move), then you can't just move to another folder.
Under KDE (you can apply to Windows too), the file is send to database to store the source (to known where recover), the original name and date.
This is done via an API, mean for Ultracopier:
- Integrate the API, mean: be more OS dependents, I need known more into win32 specific API, more specific code to maintain.
- Possible not support of thread and other limitation, mean slow down the general copy or do hurge/dirty code