quote:
Originally posted by Matti
You could however assign a system-wide hotkey to fire a script's function using the Windows API.
Well, I could see about assigning the script to be initialized when you hit Windows Key + L which is also a call to user32.dll and the LockWorkStation function. I am thinking now that a menu item on the Plus! menu makes the most sense.
Currently I have the script utilizing the messengerStart event for testing, it prompts the user with a dialog and properly handles the yes or no button events. On yes the script closes the window created by the script, locks the computer, sets your presence to away and sets a personal status message of "I'm not here right now."
I thought I remembered seeing something about taking user input? In the end if the user clicks "lock" or whatever it might be on the Plus! menu i'd a small dialog to come up and have them input a custom away message. On no it just closes the dialog.
I've also got a small to-do for storing a pre-existing status message and restoring it and the user presence upon return (if possible).
