I *love* keyboard shortcut keys, I use them all of the time I actually come from a UNIX/DOS background and I love the command line. Using the mouse is really only that great for web browsing in my opinion. That being said I just wanted to pass on a keyboard shortcut that I just remembered for Office Communicator 2005: Windows Key-Q (Win-Q).
This will open Office Communicator and take you to the "Find" field so you can type in someone's name or a phone number. I love it because I keep Communicator minimized to the tray all of the time and this just brings it up faster than I could find the button and click it. Try it out!
Do you know if this shortcut key is configurable? Like you, I'm a keyboard fanatic, and was quite surprised to find that Communicator just stole my Windows-Q shortcut key assignment that I've been using for Slickrun (another great utility for keyboard junkies!).
I *love* keyboard shortcut keys, I use them all of the time I actually come from a UNIX/DOS background and I love the command line. Using the mouse is really only that great for web browsing in my opinion. That being said I just wanted to pass on a keyboar
If you uninstall Office Communicator, then change Slickrun's shortcut key back to Win+Q, reboot, and reinstall Office Communicator, then Slickrun will get back its default Win+Q key. Of course, Office Communicator will not have a shortcut to bring it up instantly.
PingBack from http://unemploymentofficeresource.info/story.php?id=11263
It's a race condition. Both are applications are trying to register Win+Q with windows as a hotkey. The first one to do so gets it.
I fixed it by having Communicator not start automatically when windows starts. I wait until slickrun gets loaded and then use slickrun to start communicator.
For Slickrun, I exited out of Communicator so the EXE wasn't loaded. I then did the setup for slickrun which now lets you choose Win+Q. That locks it into the system. Now when you launch Communicator, it is told it can't have Win+Q. Now it has no shortcut though. You still may have a race condition on reboot so you may need to make sure slickrun loads first.
Any idea on keyboard shortcut to check the properties of a contact on MS communicator?