Brad Pedersen
New member
I would like more Bluetooth options. I hate being interrupted by text messages when I'm streaming music in my car. I really wish i could disable that.
I have so far not witnessed this myself. I've been on these forums for a while now, and your mention is the first time I've heard of it. I'm not saying you're wrong, but if that problem exists, it certainly isn't widespread. Maybe it was a problem once, but is no longer?
Anyway, even if the problem you're referring to does exist, then the solution is to ensure that a paused media player isn't using any data, because that truly would be terrible. Adding a stop button however... that is just a hack, to fix a problem that shouldn't exist in the first place. If MS used that philosophy to fix every problem, the UI would soon become an utterly useless mess.
The metro UI is all about minimalism. The best user interfaces are built by constantly asking what can yet be removed (without compromising functionality), instead of what more could possibly be "piled on". This UI design choice exemplifies exactly that. People aren't used to it, but it is good UI design.
Think about this conceptually. What is the difference (forget about bug squashing for a moment) between "stop" and "pause"? Back in the day when all we had were CD players, differing between the two made sense:
stop = stop playing music, stop spinning the disc, park the laser
pause = stop playing music, keep spinning the disk spinning, keep the laser where it it.
On todays digital media players, there is no disk to spin and no laser to park. The only thing that remains, which both functions share, is to "stop playing music". Only one common feature remains, so me might as well get rid of one of those buttons. Anything else is just about hanging on to an old habit whose time has passed.
That is why WP should not offer both options.
These are simple basic functions that have never compromised the look of any UI. So, pls forgive me, but I'm confused as to what you mean.
Imagine having two buttons for pasting text. One would clear the copy-buffer, so you couldn't paste the same text a second time, while the other would simply leave the copy-buffer as is (until you copied different text). That is equally ridiculous. There is no need to clear the copy-buffer. Doing so serves no purpose, so that button can be removed... just like stop button...
If that still doesn't make sense, then you would need to explain what it is about my previous CD player analogy that you don't understand.
Here's a thread with this issue regarding Zune in 2011: How to close or stop Zune completely? - Microsoft Community
Here's a thread from WP central more recently: http://forums.windowscentral.com/nokia-lumia-920/211005-battery-drain-problem-nokia-music.html
your comparison of a copy/paste feature is similar to clip board pasting, i.e. Copying and pasting to clip board in Windows
<snipped>
So periodically clearing out copied material from the clip board is also recommended
<snipped>
There has to be a way that the phone "remembers" where you left off when you pause a song. That means that there is some background task or data pulling, which leads to some sort of battery drainage and data loss
<snipped>
Its simple technology science
What I didn't understand is how adding a stop button interferes with the minimalistic theme.
In the second thread, the OP explicitly states that his/her problem persists without ever having played/streamed a single song. Ultimately, neither of those threads are about the "stop" vs. "pause" issue.
No, I was specifically referring to the purely text based copy/paste feature on WP, not the Windows clipboard. The amount of memory this requires is laughably little. Typically a few hundred bytes, far less than even 1Kb. There is absolutely no sane reason to expect users to actively manage and conserve such insignificant amounts of memory. It occupies not even a millionth of the memory available. Rather uncoincidentally, that is also why WP neither supports nor requires that feature from the Windows clipboard.
Comparing this to the WP copy-buffer is the far superior analogy, because remembering the position in an audio track also requires no more than a few hundred bytes of memory, which doesn't even need to be kept in RAM, but can be saved to storage. It requires no background task whatsoever. You are making what is so simple, that it barely qualifies as computer science, more complicated than it is.
Understanding why that conflicts with a particular design philosophy isn't really important.
What is important is understanding why the "stop" and "pause" buttons are logically equivalent (on digital audio players) and thus redundant. If you don't understand that, then all I can do is return to my original question, which was: "what do you not understand about the previous CD player analogy"?
Also Flash support. I know alot of ppl say that flash is becoming obsolete, but I just visited 2 websites that needed flash support and couldn't view them because of no flash. There are still alot of sites that use it.
Please stop wanting everyting you see. Flash sucks and it even slows down computers. It kills phones browsers.
Doing this for 6-12 months, there maybe a significant amount of memory lost.
Look, at this point you are just making stuff up. You can invent fake problems (your concepts about memory management) or even identify real problems as much as you like... the approach taken should always involve solving the problem.
However, what you suggest only introduces a way to work around such perceived problems, but doesn't actually solve any of them.
I would also suggest reading further than the first post in those threads you linked too, because the consensus changes in regard to what the problem is. Maybe you didn't see that.
Unfortunately, as long as you keep seeing the stop button as a solution to imaginary problems, and continue to ignore the more important point, that there is logically no difference between stop and pause on digital media players, then this discussion is going nowhere.
Good day.
Also, the Bing search bar would work better for me at the bottom like the address bar of IE...especially for taller devices.