Shoutbox

CTRL+D not working system-wide when text formatting shortcuts are enabled - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: WLM Plus! Bug Reports (/forumdisplay.php?fid=7)
+----- Thread: CTRL+D not working system-wide when text formatting shortcuts are enabled (/showthread.php?tid=99654)

CTRL+D not working system-wide when text formatting shortcuts are enabled by pstz on 09-29-2012 at 09:49 PM

When a particular formatting option is enabled in Plus! for Windows Live Messenger, the CTRL+D key combination is getting intercepted no matter which application has the keyboard focus. This is preventing other applications from responding to it.

I first noticed this a few weeks ago while I was playing a game. Tried to crouch and move right at the same time but couldn't move right because CTRL+D was effectively blocked by Plus!.

WLM version: 15.4.3555.308
Plus! version: 5.50.0.761

Steps to reproduce bug:

1. From the Plus! menu, select Preferences & Options
2. Expand Formatting and then select Formatting Options
3. Put a check next to "Enable text formatting shortcuts" (if not already present)
4. Click OK
5. Open Internet Explorer and go to any web page
6. Try pressing Ctrl+D to bookmark the page. Nothing happens!

Removing the check mentioned in step 3 and clicking OK solves the issue immediately.


RE: CTRL+D not working system-wide when text formatting shortcuts are enabled by pstz on 09-30-2012 at 04:34 PM

Interesting...

Yesterday, switching this option on/off was definitely having an effect on the CTRL+D combination.  I observed it multiple times.  But today it no longer does.  Furthermore, what seems to have caused the problem is a different program.

The culprit was a program named CallCenter (companion to the Android app of the same name).  I terminated it and CTRL+D came back to life.  Checking its options dialog revealed that a CTRL+D hotkey had been set up.  I promptly disabled this.

Looks like this has potentially been a false alarm, but please do quickly check to see if you can replicate the problem at your end.

Thanks!