At the risk of incurring further snark from you, I don't think that's quite what the poll says. It could easily be rephrased "Have you at any time missed a slider control" and be no less true.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
User Experience Poll on the new Control Panel
- Thread starter freepomme
- Start date
- Sort by reaction score
At the risk of incurring further snark from you, I don't think that's quite what the poll says. It could easily be rephrased "Have you at any time missed a slider control" and be no less true.
Yeah..No. it states that 50% of the people have accidentally done it. Doesn't make it a problem. I've said I've accidentally done it, but it is not a problem for me. It hasn't happened in weeks.
Most polls on MR are lacking in exact wording, or available choices, which is why the thread comments help to clarify the results. Seeing this question as asking if even once this happened, is ridiculous. It obviously implies do you find this particular control problematic.
No it doesn't. I certainty did not take it as a "problem". If so I change my answer.
It's a very specific question. Has it happened. Saying it happened does not imply it's a problem.
As mentioned earlier in the thread, auto brightness doesn't work as desired for some. It also has nothing to do with whether this control is implemented correctly, and the wider issue of the two-panel control center.
[doublepost=1474242521][/doublepost]
What value is there in knowing whether, one single time, you missed a control slider? Should I start a poll, "Have you ever missed the "r" key when typing?" Wow, that would be valuable information to have...
I apologize if you haven't gone to college, but this is very basic critical thinking.
Last edited:
Ha you're funny. I'm in law school. It's not critical thinking it's about being extremely specific. I'm sorry if you can't comprehend decoding the question as a whole.
It's clearly stated "ACCIDENTALLY". That's not implying "are you constantly sliding the control panel". If the phrase was "constantly sliding", then that applies a problem.
What in the world does that mean? And besides education has absolutely nothing to do with reading the question as it's specifically stated.
It always happensWhen changing the brightness, the new control panel moves to the side when you're trying to adjust it.
Please state what you think about the new Control Panel.
When changing the brightness, the new control panel moves to the side when you're trying to adjust it.
Please state what you think about the new Control Panel.
I do this sometimes. I find myself being more careful when using the brightness slider. I'd like it if they made the slider-thumb larger so it was easier to grab.
The Control Panel isn't hard to use... and it's not broken or anything, I mean it works. It does what it's supposed to do....
you just can't do it too fast.
If you're trying to navigate around iOS faster than the iOS can go... this results in user error.
For example, you can only close windows in safari at a certain speed. Try to go faster than that, and eventually you're going to swipe on a window and nothing will happen.
Trying to use the Control Panel too fast is going to result in touches not being registered.
I am squarely on team "big button". I'm tired of them squeezing more and more buttons into minuscule spaces. That old slider that was 1 millimeter wide was the worst. I wish the music app had a setting to place only two buttons on the screen: play and pause, each taking half the screen.
The volume slider on the music panel suffers from the same problem. Anything other than a direct hit right on the dot, with a very firm unwavering press, is interpreted as trying to slide the entire panel.
This behavior is contrary to 7 years of slider control programming in Apple touchscreen products.
No one is a bigger fan of iOS than me, but this new control panel is a major fail. It's nearly unusable on the go, which is exactly when I need to adjust brightness, etc. All those saying it works great, try walking down the street dodging pedestrians and other obstacles while you do it.
This behavior is contrary to 7 years of slider control programming in Apple touchscreen products.
No one is a bigger fan of iOS than me, but this new control panel is a major fail. It's nearly unusable on the go, which is exactly when I need to adjust brightness, etc. All those saying it works great, try walking down the street dodging pedestrians and other obstacles while you do it.
Some of the comments here make it sound like I have to be a master marksman to adjust the volume and brightness controls. Just tried it and I can't say I am experiencing any difficulty adjusting them in the very least. And I am doing this one-handed on my 6S+ while walking.
Happens to me all day everyday, I hate it. Apple continues to dumb down and degrade iOS input with every revision of iOS it seems.
I also find annoying the excessive rubber banding, why do I need control center to rubber band at all if I'm just trying to adjust brightness towards the right for example?
I also find annoying the excessive rubber banding, why do I need control center to rubber band at all if I'm just trying to adjust brightness towards the right for example?
Do you all having the issues just immediately start sliding your finger across the screen while putting your finger on the screen in one motion or do you place your finger on the slider dot and then after a slight hesitation slide? I've found you do need to let it register that you are trying to control the contrast or volume vs just swiping across the screen to switch which screen you are on and happen to be doing it on the slider bar.
Apple loves the rubber-banding. It's all over the Apple Store app, even where there's no reason for it, like a single product with no other versions. Here I am pushing the watch image out of view, for no apparent reason:
I think it's ironic because Google had to come up with an alternative due to Apple owning a patent on it, and Android's alternative is without question superior. Why? Because Android's solution gives you a visual cue, but it doesn't block user input. Apple's rubber banding looks pretty but interferes with user input.
Can anyone provide a valid reason for needing a huge Night Shift button in Control Center? Who the hell is switching Night Shift on and off on a regular enough basis to even justify it being in CC at all? I thought the whole point of Night Shift was to possibly provide better circadian rhythm by adjusting the screen temps during certain times every day? How could it possibly provide any benefits if someone is switching it on and off every other day? Just leave it in the settings menu where it should be and move the music controls back to the single card CC. Or at the very least make the damn button smaller. There's no reason the flashlight button should be 1/8th the size of Night Shift when it actually serves a very useful and valid purpose in CC.
Happens to me all the time. Its frustrating! Unless you have PINPOINT accuracy or small fingers, its hard to quickly access the notification screen and adjust brightness.
[doublepost=1475098512][/doublepost]
100% agree. I've never manually turned on Night Shift. That's why I like having a time schedule for it. It is a bit confusing that Night Shift, the button I never use, gets the most real estate on CC. It would be nice if we could adjust CC, and customize which buttons appear.
HEY! I've never used the Night Shift button either! NOT ONE TIME. NOT ONCE!
He's right. He's absolutely right!
And you know what? I guess Apple never got the memo that Night Shift serves no purpose... as reported by numerous online publications.
http://www.theverge.com/2016/3/29/11326194/apple-night-shift-blue-light-sleep
The problem that night shift tries to solve is actually better solved with the new Display Accommodation Settings in Accessibility Settings.
¯\_(ツ)_/¯
But of course Apple doesn't know any of this.
This all falls down on the fact that their LCD screens are truly inferior.
Last edited: