ctrl+dot not working in mac os mojave

[iamluqi]

Just got slickedit installed on the mac os mojave, but it looks the ctrl+dot does not work; nothing happens when pressing ctrl+dot upon a symbol; nor could I define the keybinding with ctrl+dot while ctrl+, or ctrl+/ both work. is this a known issue related with mac release? tried different versions but no help.

[Clark]

Haven't heard of this issue. I'm using Mojave. Although, every now and then we find a new input method editor issue. It sounds like SlickEdit is unable to receive the Ctrl+Dot key press. Try typing Ctrl+Dot in the "Search by key sequence" text box of the Key Bindings dialog (Tools>Options>Keyboard and Mouse>Key Bindings). If SlickEdit is recognizing this keypress, it should show "Ctrl+." in the text box.

[iamluqi]

yes, exactly when i type the ctrl+dot keys, there is no display on the gui dialog. i feel it is the gui interface is blocking this key combination for some reason.

[Clark]

What keyboard layout are you using (macOS  Keyboard>Input Sources Tab)?

These are the possible causes I can think of:
* Keyboard layout/Input method - Could be a new issue we haven't seen yet
* macOS window manager has an override for this key. SlickEdit does not take any keys away from the macOS window manager (ex. Ctrl+Left is taken over by macOS window manager -- SlickEdit never sees this key).
* Some odd driver or product installed - Haven't seen a macOS driver or product causing a keyboard issue yet. Doesn't mean it won't happen for sure.
* keyboard has a dead key (too obvious -- so probably not this)

[iamluqi]

yes, i was suspecting macos is taking this special key set but if I set the ctrl+dot in the macOs key binding it sees the combine and works. otherwise if just press ctrl+dot in MacOs no action seems happening. I had this issue on two different mac pro's manufactured at different years with the OEM keyboards. Is there any tool to debug where typed key binding goes?

[iamluqi]

k, figured out the reason. There is some other input source type that takes in the ctrl+dot combo so the app could not see it.

[Clark]

Let us know how you work around this and/or what caused this. It might help someone else. Glad you figured this out.