Re: Custom Copy roadmap
Posted: 24 Aug 2011 21:41
Don't put the cart before the horse...
NOTHING is in Windows 8 until it ships.
NOTHING is in Windows 8 until it ships.
Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Very true -- but if something made it to that point (published on that blog), and with all the resources M$ has, it's at least good research to know some ideas that XY might be able to adapt from and thus be able to compete better...even now before it gets finalized.TheQwerty wrote:Don't put the cart before the horse...
NOTHING is in Windows 8 until it ships.
Oh yes, I did not think of this. But "Moving"? It's not what's happening at that point. Hmmm....zer0 wrote:Is there a reason why -- when a custom move is in progress -- the caption above the progress bar reads "Copying"? I appreciate that moving is essentially copying and deleting source, but using that word is inconsistent with the rest of the dialogue window and can potentially cause confusion.
While you're right, I did expect "Moving" as a caption since that's the file operation that I triggered. Seeing a different caption made think I was copying a file by mistake, had me checking that it was moved after all, etc. Is an extra workout for the brain really necessary?admin wrote:Oh yes, I did not think of this. But "Moving"? It's not what's happening at that point. Hmmm....zer0 wrote:Is there a reason why -- when a custom move is in progress -- the caption above the progress bar reads "Copying"? I appreciate that moving is essentially copying and deleting source, but using that word is inconsistent with the rest of the dialogue window and can potentially cause confusion.
agreed with that point.!zer0 wrote:I did expect "Moving" as a caption since that's the file operation that I triggered. Seeing a different caption made think I was copying a file by mistake, had me checking that it was moved after all, etc.
In intra-volume move there is nothing written so "moving" and "moved" is better I think.TheQwerty wrote:By the same logic it shouldn't be "Bytes copied".
Why not eliminate the difference and use "Writing" / "Written"?
But nothing really is moved here - only renamed?admin wrote:In intra-volume move there is nothing written so "moving" and "moved" is better I think.TheQwerty wrote:By the same logic it shouldn't be "Bytes copied".
Why not eliminate the difference and use "Writing" / "Written"?
If you want to get pedantic about it, there's more written than there is moved, is there not?admin wrote:In intra-volume move there is nothing written so "moving" and "moved" is better I think.
I think zer0 was right. This is just about labels, and when you move you expect and like to see "move", "moving", "moved". It makes the user feel confident and cozy.TheQwerty wrote:If you want to get pedantic about it, there's more written than there is moved, is there not?admin wrote:In intra-volume move there is nothing written so "moving" and "moved" is better I think.
The MFT has to be updated so something somewhere is being written.
The only reason I suggested it is because it would lessen the logic in updating those dynamic labels.
AFAIC, you can calling it "zigging" and "zagged".
I'm pretty sure nothing would make the user feel more "warm and toasty inside" than "zigging" and "zagged".admin wrote:I think zer0 was right. This is just about labels, and when you move you expect and like to see "move", "moving", "moved". It makes the user feel confident and cozy.
i wish this appear at some program reallyTheQwerty wrote:The teleportation of your bits is now complete.
May the rest of your day be pleasant!