Custom Copy roadmap

[TheQwerty]

It would be nice if there was an option or tweak to avoid the progress dialog on small jobs; defined by duration, size, or item count.

[admin]

1. You mean remove it from the source files?

2. Depends. What you wish has been the behavior before it was changed some years ago:

Code: Select all

v5.10.0000 - 2006-08-24 10:48
    * Backup/Backup To...: Before, when you cancelled the "Save Backup 
      Log As" only the logging was skipped but the backup was performed. 
      Now the whole backup operation is cancelled.

[Stefan]

Stefan>Add an option to remove archive attribute flag from copied files
Admin>You mean remove it from the source files?

Ohh i see

No. I was thinking about the target.
If i copy, the copies are virgins then there and not modified.
But right, the source are now copied and could be switched to virgin too,
so on an later copy action only the newly modified files could be copied.
Like Backup-Tool works.

[ ] Remove archive attribute from Source
[ ] Remove archive attribute from Target (i think that does an backup tool anyway?)


An quick test with XY backup shows that the A-attr is not reset here too. (i was thinking i had see that option somewhere)


But i can also argue that we should not do anything on the source.

So an more general idea:
[ ] Execute script before process
[ ] Execute script after process
and by using the selection or parsing the log file we can do what we want ourself.


----

Stefan>i only wanted to cancel the creation of the log file for this case, not the copy action
Admin>Depends. What you wish has been the behavior before it was changed some years ago:

I see. I can understood both sides.
With my description we could work with more flexibility (this time an log, next both times not, then an log again)
but i see that one may guess to cancel the whole operation when he cancel the Save as...-Dialog.


.

[admin]

Yes, let's leave complications for later...

[TheQwerty]

It would be nice if there was an option or tweak to avoid the progress dialog on small jobs; defined by duration, size, or item count.

Another nicety would be to either remove the transfer rate from the progress window's title or only update it when updating the percentage.

It's distracting seeing it rapidly change on the task bar, especially when the length of the string changes as well.

[admin]

It would be nice if there was an option or tweak to avoid the progress dialog on small jobs; defined by duration, size, or item count.

Another nicety would be to either remove the transfer rate from the progress window's title or only update it when updating the percentage.

It's distracting seeing it rapidly change on the task bar, especially when the length of the string changes as well.

Agreed.

[grindax]

.

[nas8e9]

How about making move operations that consists of a copy followed by a delete (e.g. cross-volume moves and moves to/from network locations) also use Custom Copy?

+1, although I suspect that may not make 10.0.

Regardless, one of the advantages of Custom Move would be adding to the Safe Overwrite for Custom Copy if verification is enabled: copy the file but don't delete the original until the hashing confirms source and destination are identical.

[admin]

How about making move operations that consists of a copy followed by a delete (e.g. cross-volume moves and moves to/from network locations) also use Custom Copy?

+1, although I suspect that may not make 10.0.

Regardless, one of the advantages of Custom Move would be adding to the Safe Overwrite for Custom Copy if verification is enabled: copy the file but don't delete the original until the hashing confirms source and destination are identical.

Yep, is planned.

[zer0]

I am still not entirely clear -- is the purpose of XYcopy 2.0 to allow more flexibility as far as copying is concerned rather than improvement of how fast files are actually copied? Or is the latter reserved for XYcopy 3.0?

[admin]

I am still not entirely clear -- is the purpose of XYcopy 2.0 to allow more flexibility as far as copying is concerned rather than improvement of how fast files are actually copied? Or is the latter reserved for XYcopy 3.0?

Both, but for now I focused on flexibility and safety.

[zer0]

I am still not entirely clear -- is the purpose of XYcopy 2.0 to allow more flexibility as far as copying is concerned rather than improvement of how fast files are actually copied? Or is the latter reserved for XYcopy 3.0?

Both, but for now I focused on flexibility and safety.

OK. In the meantime, I will test another proggy to see how high I should set my expectations.

P.S. I take it that you changed your mind about XYcopy 2.0 being available to Pro licensees only? I suppose it takes the headache of developing another big feature for Standard buyers.

[admin]

P.S. I take it that you changed your mind about XYcopy 2.0 being available to Pro licensees only? I suppose it takes the headache of developing another big feature for Standard buyers.

Yup!

[Zodler]

I don't know if this has been discussed or not but it would be great to have Windows 7 Task Bar Progress like the native copy/move.

It would even be greater than the native copy to show the complete queue as a progress bar in taskbar and not just the current job as is with the native copy.

[admin]

I don't know if this has been discussed or not but it would be great to have Windows 7 Task Bar Progress like the native copy/move.

It would even be greater than the native copy to show the complete queue as a progress bar in taskbar and not just the current job as is with the native copy.

1. planned
2. that would rather have to go to XY's statusbar