Page 8 of 9

Re: Custom Copy roadmap

Posted: 24 Aug 2011 21:41
by TheQwerty
Don't put the cart before the horse...
NOTHING is in Windows 8 until it ships.

Re: Custom Copy roadmap

Posted: 24 Aug 2011 21:52
by admin
So far I like what I see about Win8. After the Vista/7 desaster it might be the next good MS OS.

Re: Custom Copy roadmap

Posted: 24 Aug 2011 22:52
by j_c_hallgren
TheQwerty wrote:Don't put the cart before the horse...
NOTHING is in Windows 8 until it ships.
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.

Re: Custom Copy roadmap

Posted: 20 Sep 2011 20:42
by zer0
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.

Re: Custom Copy roadmap

Posted: 20 Sep 2011 20:46
by admin
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.
Oh yes, I did not think of this. But "Moving"? It's not what's happening at that point. Hmmm....

Re: Custom Copy roadmap

Posted: 20 Sep 2011 21:12
by zer0
admin wrote:
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.
Oh yes, I did not think of this. But "Moving"? It's not what's happening at that point. Hmmm....
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?

Re: Custom Copy roadmap

Posted: 20 Sep 2011 21:19
by TheQwerty
By the same logic it shouldn't be "Bytes copied".

Why not eliminate the difference and use "Writing" / "Written"?

Re: Custom Copy roadmap

Posted: 20 Sep 2011 21:48
by eil
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.
agreed with that point.! 8)

Re: Custom Copy roadmap

Posted: 21 Sep 2011 08:02
by admin
TheQwerty wrote:By the same logic it shouldn't be "Bytes copied".

Why not eliminate the difference and use "Writing" / "Written"?
In intra-volume move there is nothing written so "moving" and "moved" is better I think.

Re: Custom Copy roadmap

Posted: 21 Sep 2011 09:47
by PeterH
admin wrote:
TheQwerty wrote:By the same logic it shouldn't be "Bytes copied".

Why not eliminate the difference and use "Writing" / "Written"?
In intra-volume move there is nothing written so "moving" and "moved" is better I think.
But nothing really is moved here - only renamed?

It seems it's just playing with words? And meanings?
(And knowledge of people. As it seems MS plans people not to know what is physically done - only the result. Else they needed to know things about the filesystem that "isn't neccessary"...)

Re: Custom Copy roadmap

Posted: 21 Sep 2011 12:42
by TheQwerty
admin wrote:In intra-volume move there is nothing written so "moving" and "moved" is better I think.
If you want to get pedantic about it, there's more written than there is moved, is there not?

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". 8)

Re: Custom Copy roadmap

Posted: 21 Sep 2011 12:47
by admin
TheQwerty wrote:
admin wrote:In intra-volume move there is nothing written so "moving" and "moved" is better I think.
If you want to get pedantic about it, there's more written than there is moved, is there not?

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". 8)
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.

Re: Custom Copy roadmap

Posted: 21 Sep 2011 13:06
by TheQwerty
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'm pretty sure nothing would make the user feel more "warm and toasty inside" than "zigging" and "zagged". :wink:

To whom it may concern,

The teleportation of your bits is now complete.

May the rest of your day be pleasant!

Re: Custom Copy roadmap

Posted: 21 Sep 2011 13:18
by admin
:lol:

Re: Custom Copy roadmap

Posted: 21 Sep 2011 16:00
by eil
TheQwerty wrote:The teleportation of your bits is now complete.
May the rest of your day be pleasant!
i wish this appear at some program really :D