Both work for me. I updated to OS X 10.10, Yosemite, this morning. I'm using FMP 13.0v3.
I've been using it all day and I use shortcuts a lot. I haven't found any (yet) that don't work.
Whenever I've heard of this issue its been a third party key substitute or Macro utility. Do you have anything like that?
Nope. The indicated commands are available from the View and Edit menus, respectively, but the right side of those menus lists keyboard shortcuts like ⌘-B and ⌘-F (but not ⌘-L) under View and ⌘-C and ⌘-V (but not ⌘-D) under Edit, so it's FileMaker itself which doesn't permit them, not that they're being overridden by some 3rd-party utility.
OTOH, my repeated attempts to hit ⌘-L and ⌘-D didn't seem to produce any other sort of action, either, so I'm not sure what use the OS thinks it's making of them.
I'm curious that they do work for you, tho. I'm running a pretty plain-vanilla environment, so I wonder what the difference is between your setup and mine.
work for me as well, what version of FM are you using?
I also experience failure of keyboard shortcuts after a while under Yosemite. Running FMPA 13.0v3. No third-party plug-ins etc.
If I quit FileMaker then launch it again, the shortcuts work OK for a while, then sotp working.
I always use the most recent available version of both FMP and FMPA, so 13.0v3.
- Any chance a custom menu might have loaded the wrong menu set?
- Or a different privilege set group having limited access to layout mode or duplication actions?
Good things to check, but I don't use either (plain vanilla setup), so no.
I had a problem a few weeks ago in a session where the Manage Layouts option wouldn't trigger from the layout popup menu in layout mode, but I was running the latest Mavericks and latest FMAdv. That also went away after a reboot, and, knock on wood, hasn't resurfaced.
I am still in the Waiting for More Reports before Upgrading Mode regarding Yosemite, being a follower of the school that says one's OS should be the oldest piece of software one is running — at least until other people have put it through long hard paces.
I think it's fixed. Tried rebbot, repair m=permissions, noe of that helped. However, I then trashed FileMaker Preferences then launched FileMaker and it has been working fine since.
Old Mac lesson relearned: When an application is misbehaving, sometimes trashing the Preferences file for that applicaiton will cure the problem.
Find Preferences in your user Library, Preferences folder, com.filemaker preferences
"Old Mac lesson relearned: When an application is misbehaving, sometimes trashing the Preferences file for that applicaiton will cure the problem" Tis a good point, that. It reminds me that I used to have to do that with sufficient frequency to remember it. I guess it shows how advanced Apple hardware and operating systems have become that we hardly ever have to do such things these days.
I think this is related to the bug (described elsewhere here) that causes certain keyboard shortcuts to disappear on Mac. Not related specifically to 10.10. It happened under 10.9 also, but then only affected the cmd+L command (for me). Under 10.10 the Omit Record command (cmd+T) also vanishes. It seems to be when one is scrolling through the fields in Define Database that causes the commands to disappear.
Hoping for a fix from FileMaker soon.
Good news, I guess.
Yosemite is off the hook. A different computer, still operating under Mavericks, had the same problem crop up. So it’s some oddity in FMP and FMPA. It can’t be custom menus in my case, tho, because I’m not using them. Nor am I using any utility that remaps keyboard shortcuts.
Intermittent errors are, of course, the worst kind, but at least this is one with a readily available workaround: simply use the still-available menu command.
Next time it happens, I’m gonna relaunch FMP and see if that fixes it.
I found that trashing the FileMaker preferences file (in my Mac User library) then launching FileMaker again cured the problem. Apparently the Preferences file got corrupted somehow. This is an old Mac method that often works for curing misbehaving applications — relearned it again on this issue.
I wrote a reply to this effect on the Technet thread.
Indeed! I went to your school too!
Sent from my iPad
11th Hour Group Pty Ltd