Cannot assign Ctrl-Opt-Cmd-L to Menu Keys on OS 10.9.4

[NisusUser]

I have assigned a Menu Key Ctrl-Opt-Cmd-L for changing text to a certain language. It's easy since you just hold down the three keys in a row and type "L". That works fine on Snow Leopard (10.6.. However, on another computer I have Mavericks (10.9.4). Nisus will not allow me to assign Ctrl-Opt-Cmd-L to any Menu command? Does anyone know why? Is this something specific to Mavericks? I have tried all the other keys on the keyboard, and Nisus will accept them all with Ctrl-Opt-Cmd. But not "L" (actually not upper case). Strange … Any ideas?

[martin]

I just gave it a try on OS X 10.9.4 with NWP 2.0.7 and had no trouble. Command + Option + Control + L was assigned to a menu and activates successfully.

Some questions:
1. Do you see the shortcut displayed on the menu you assigned it to, eg:

menu.png (17.48 KiB) Viewed 4083 times

2. Do you have your OS X system preferences configured to use that shortcut? ie: under System Preferences > Keyboard > Shortcuts. Perhaps you have a system wide shortcut that's overriding NWP.
3. Have you installed any other software that manages shortcuts, input methods, text expansions, etc? If so, perhaps they are interfering.

[NisusUser]

1. Do you see the shortcut displayed on the menu you assigned it to, eg: [deleted image]
2. Do you have your OS X system preferences configured to use that shortcut? ie: under System Preferences > Keyboard > Shortcuts. Perhaps you have a system wide shortcut that's overriding NWP.
3. Have you installed any other software that manages shortcuts, input methods, text expansions, etc? If so, perhaps they are interfering.

First of all, thanks for responding, Martin.

As it turns out, the problem was solved by following Hamid's advice here about copying all NWP settings to another computer. The Ctrl-Opt-Cmd-L shortcut copied over just fine. (http://www.nisus.com/forum/viewtopic.php?f=18&t=5789.

But I did check for answers to all your questions:
1. No. Not until I copied over settings.
2. No. It was pretty much a clean install of Mavericks.
3. None that I know of. Fact is I did use "Migration Assistant" to move all apps from the SL machine to the Mavericks machine. I don't use any of those shortcut apps, but I do have some latent on the SL machine, so maybe they moved over and caused a conflict.

In any case, the case is closed for now, and I'm a happy camper. Thanks!