Shoutbox

How to reproduce the bug :
You should have two messenger accounts that have different settings :
  1. messenger with lock activated (ctrl + space).
  2. messenger with lock desactivated.

Log with the first one and check that the lock is working (type ctrl + space), now logout and log with the second one, AND DONT OPEN PREFERENCES of msg+, type anywhere (ctrl + space) then messenger is locked!

This bug becomes really annoying if you use a lot the (ctrl + space) combinaison , example IntelliSense in visual studio.

Possible way to solve that
Every time an account logout, msg+ should remove ctrl + space hook and when an account logs it should override preferences.

I hope that you fix this problem as soon as possible! Sorry for my poor english.

First thing to know:
Using multiple messenger programs is not officially supported by Microsoft and using the multi-msn (aka polygamy) feature has its limits. This is one of them...
You can't have the same shortcut to lock Messenger for both Messenger programs. Doing that will obviously overwrite the first Messenger instance's shortcut, and you will instead lock the second one.

You need to set different shortcuts for each Messenger account if you're planning to use those accounts in conjuction with multi-msn/polygamy.

--

Second, if you don't like the shortcut being used for Messenger lock, because it conflicts with one for another program, then you can/should change it in the preferences.

...misread

I said that you should have two messenger accounts, this bug happens with a single instance of messenger, if you log with the first account that have lock activated and you logout, then you log with the second one which have lock desactivated, the lock still work!

Already reported. Messenger Lock staying enabled

quote:

---

Originally posted by Chris Boulton in How to report a bug (READ) thread.

• Do not report duplicate bugs; before posting your bug report, have a look around the forum for a similar bug and check to see that it is actually a bug and its not a fault on your behalf.

---

Yeah, I have also noticed this bug, but I haven't tried to reproduce it. It's very annoying.