@ T3slider --

I do not think so, I suspect it will always select 'logout' because it is using the keys, rather than causing a mouse click; thankfully I will not be testing that theory as I haven't used Winbloze for quite a long time now. I did however examine the goofy macro on the roommates Win machine.

Well I am rather sick/under the weather the last couple days and have mainly been in bed, but I DID manage to get my "Browser Search" button to work and it was pretty easy, using xbindkeys.
I still am not certain whether the goofy-macro keys will be useable yet, but xbindkeys DOES have some sort of timing monitor (I think it can determine how rapidly a series of keys are pressed) and from XEV I see that as you would expect, the goofy-macro key sequence is emitted MUCH faster than I can actually type the 4 keys myself. So if it can use the speed of a sequence as a determinant, then the goofy macro will be workable.

If I get goofy-macro to work I'll post again on it.

Sasha

NOTE - If you run xbindkeys, kill the running instance before starting it afresh. Also, do not forget the & at the end of the commands you put into the configuration. Finally, if you find that while playing with xbindkeys, a wrong config option will cause your xterms to become non-responsive. You will need to physically click out of X to a VT (F1-F6 or whatever) and login and use 'killall xbindkeys' then return to your X VT-7 and try again.