6/11/2023 0 Comments Ios9 keynote![]() ![]() Completely quit Numbers, Keynote, or Pages - whichever program you're having an issue with - on the computer or device in question. ![]() ![]() Fortunately the solution is fairly simple. ![]() Static case is a hangover from not having a choice on physical keyboards.If you aren't able to open a file or document in Pages, Keynote, or Numbers that's saved in iCloud, it's most likely caused by a syncing error. I would gather that at some point physical keyboards will get as dynamic, and the letters will change to indicate the actual letter case just the same. It’s a stretch to argue that typing a lower-case letter, and seeing a lower-case letter on a keyboard will present a problem. This new solution is more elegant, makes more sense, is more in-line with how we write and interpret writing, and is more in tune with how the human mind processes information. However, I should note that special needs keyboards come with lower-case keys because it’s less confusing for minds that have trouble with these kinds of things.Īnyhooo – the blue button isn’t the panacea here. Now, if you’re arguing that this change will make it more difficult to type for a person who can only read an upper-case alphabet, then you may have a point. These are letters of the alphabet that are burned into the mind of anyone who can read from the age of 2 through death. Extending this to the elderly, you’d be hard-pressed to argue that showing the actual case being typed would be more confusing than showing them a case that is opposite their intent.Īs well, these aren’t 26 new symbols. One could easily argue that there is a cognitive hangup due to wanting to type a lower-case a, and when you look at the keyboard the only A you see is upper-case. Unless the person is illiterate…which is another problem unrelated to this dialogue, and not Apple’s fish to fry. There isn’t any extra mental work involved as there isn’t a new decision happening, aside from selecting caps, which already happens…except as of now, you hit caps and the only indication of change is the caps button, which isn’t ideal.īeyond that, the brain will process a lower-case e just as it would a upper-case E. You’re positing a decision between the two, however one is only presented with one or the other at any given time. The brain isn’t making a decision between upper-case or lower-case. I understand what you’re aiming for – but this simply is not how the human mind works. and Ph.D in this stuff…so I’m not coming at this from outer space. Introducing a new color would call out that this key works differently and should not be confused with the other function keys or alphabetical keys. It stays active after being pressed vs the others that only look active when you are currently touching them. Shift also doesn’t behave like any other key. This makes it harder to process what state the shift key is on. Yes, learning white = on is easy except that all the alphabetical keys are always white and shift is right next to them. You are also missing something about the current implementation and it again has to do with spacial relation to other keys. Now that schema is changing, but instead of my solution, which would require users to understand one new symbol, this one requires people to process 26 new ones in an instant.įine if you are already comfortable touch typing on glass, but less so for elderly who have a harder time at seeing and less coordination. Physical keyboards and previous apple ones have established that the only character you need to look for is the capital form. That keys are represented by consistent icons is a schema too. But you find them by seeing their spacial relation to other keys don’t you? So if you are looking for a key and can’t find it immediately where you thought it would be (because it doesn’t look like what you were expecting) then you look around and it takes a second to processes that oh I’m in lowercase now. ![]()
0 Comments
Leave a Reply. |