'Define as Placeholder Text' shortcut problems
Hello,
Does anyone else find that the shortcut for defining text as a placeholder doesn't work?
Thanks,
Calum
MacBook Pro with Retina display, macOS High Sierra (10.13.1), MBP 15-inch, Mid 2015
Hello,
Does anyone else find that the shortcut for defining text as a placeholder doesn't work?
Thanks,
Calum
MacBook Pro with Retina display, macOS High Sierra (10.13.1), MBP 15-inch, Mid 2015
Peter writes: "control option command t works on my Pages 6.3.1."
Control-option-command-t also works on my Pages 5.6.2. (Which won't be the version Calum is using, assuming he has correctly idntified his operating system.
The same keystroke combination was used in Pages '09, but may be broken in OS X 10.11.x and macOS 10.12 and 10.13. With my Pages '09 (v4.3), using the menu choice of the key combination to 'Define (selected text) as Placeholder text places a blue boundary around the selected text, but typing one or more characters with the insertion point inside that boundary does not immediately replace the 'placeholder text' with the entered characters, as it would with 'real' placeholder text.
Regards,
Barry
Are you holding down the shift key, or have the Caps lock on? Because it is not a capital T.
Failing that you have something else that is catching the keyboard shortcut. Have you installed anything else lately?
Peter
Hi Peter,
Thanks for your willingness to help.
I've just been on the phone with Apple Support and found the problem.
I use a Logitech MX Master 2S mouse (https://www.logitech.com/en-gb/product/mx-master-2s-flow), which, from memory, I know recently had an update to its software. The problem seems to be with a system LaunchAgent "com.logitech.manager.daemon.plist"... it is such a random, small thing that I don't even know where to start. I have at least I found the problem though.
Thanks again for your support.
Calum
Ian
That has been a widespread UI error with Apple since forever.
There is no need for Apple to capitalise the shortcut other than some misguided and inadvisable sense of aesthetics.
The failed logic is most exposed when Apple sets the keyboard shortcuts for increase/decrease font size and chooses to add shift for + and not for - because the + is on the uppercase of the keyboard. And as usual the iOS team goes off all on their own when it places both the + and the - on the lowercase of their keyboard.
Peter
And what do you think that is?
In what version of Pages?
control option command t works on my Pages 6.3.1.
Peter
Thank you both for the replies.
@Peter - I am using the same key commands as yourself, on the same version, but with no luck..
@Barry - Correct, the shortcut used to work in the old versions!
I'm going to contact support to see if there is something I'm missing; I'll update here if there is anything of note.
Thanks again!
Calum
Apologies, Peter, but I'm not 100% sure I understand what you mean.
To be complete: the Logitech Options app is the accompanying software for the mouse, which, when configured by the user, obviously/apparently references this pesky plist file! Everything was working correctly in the past, so it must have changed in some way in the most recent update... for it to affect such a specific/random shortcut is just strange and partially unlucky, I think!
Thanks again for your help.
Calum
More likely due to the original Mac keyboards (and the current ones, for that matter) having the letter keys labeled with upper case letters.
In iOS, + and - (and @) are on the numbers 'keyboard', which in the current version has both an 'upper' and 'lower' 'case' set of characters.
Regards,
Barry
…and for consistency's sake should have the same upper and lower case position for characters as the Mac and PC keyboards.
Apple seems to think Contextualism is having to be extremely conscious of what hardware, software and Operating System you happen to be using all the time, and have to constantly adjust accordingly.
What we are having to actually adjust to is massive amounts of wasted time, misunderstandings due to word substitution, spelling errors and our productivity being flushed down the toilet.
Peter
"…and for consistency's sake should have the same upper and lower case position for characters as the Mac and PC keyboards."
In an ideal world, that might be so. In this one, not so much.
Difficult to achieve, when trying to cram a keyboard onto the space available on an iDevice, especially a phone.
The first step was to reduce the number of keys—stripping off the entire row of Fkeys and the row containing the numerals (and the +, -, = and _.
Consistency hasn't been a major factor in keyboard layout. The Sholes layout of the letters puts the left hand fingers to far more work than those on the right hand and actually slows down an experienced typist. But it's 'consistent' with past practice, and difficult to change due to that past practice. Then there's the keyboard arrangements of the numbers on a number pad or 10 key calculator and on a telephone. On the pulse dial telephone, the zero is actually a 10—it sent 10 pulses of power down the line to make a relay move ten positions to the correct contact to route the call to the called number, and logically, it was placed at the bottom of the array, after the 9, just as it was on the dial. On the calculator the 0 was a zero, not a 'ten'. It occupied the same physical position on the 10 key array, but came before the 1, not after the 9, as the rest of the numbers increased as the 'moved' right (like the ones on the phone) and UP (opposite) to the ones on the phone.
Regards,
Barry
So to clarify for the viewers, I am just guessing, what you were actually doing is programming a button on your mouse to act as the keyboard shortcut?
Peter
'Define as Placeholder Text' shortcut problems