| here's my config for Fvwm/xmms2: | | DestroyFunc Xmms2 | AddToFunc Xmms2 | + I Exec exec xmms2-launcher | + I Exec exec xmms2 playlist shuffle | + I Exec exec xmms2 playlist play | + I Silent Key KP_Right A S Exec xmms2 server volume +2 | + I Silent Key KP_Left A S Exec xmms2 server volume -2 | + I Silent Mouse 4 A S Exec xmms2 server volume +2 | + I Silent Mouse 5 A S Exec xmms2 server volume -2 | + I Silent Key Pause A C Exec xmms2 toggle |
It never ceases to amaze me that Linux people will think it's impressive to say things like: "Hey, I can do that with 27 lines in a console window. You poor Windoze people have to click a button or something." Since 1995, few people will be impressed that you can control a music player without using a UI of any kind. They'll be even less impressed that they can write excessively bloated and abstruse config entries for custom commands. You may find it hard to believe, but that just isn't a compelling salespitch.
(Not to mention the only-geeks-could-love-it naming traditions. Anything named Fvwm/xmms2 has no right to exist. :)
| It's just as simple to tell the WM to select a window | and generate synthetic keystrokes if the player doesn't | already have a command interface. | Of course selecting a window with the WM will make the | window active, you'll have to first capture the active | window and switch back. |
Yes. The whole point was to send messages to windows that are not active, without changing the active window. He doesn't have any problems with sending his commands, as I read it. He just wants to send them to a non-active window. I don't know of any way to do that, and if you could it would require both a specific OS functionality and a target process that's designed to listen somehow. The system sends input to the active window. So it seems the target process would need to be hooking into all input, like a sort of super keylogger, since its window is not receiving the input. The target software would have to be designed for that purpose in the first place and would have to provide config options for it. Once that's solved, you'd need to figure out how *not* to send the specific input to the active window. That would mean having something like a Control Panel applet that lets you configure details of which processes can receive input from which devices. (Or on Linux, of course, it would require that someone online has posted 53 lines of interminable gobbledygook that you can enter into a console window to accomplish the same thing.)
Maybe all of that exists and is possible on your Linux Miracle, but I don't see how. ...But at least you don't have to use a chisel and a stone tablet, so I guess Linux may not be far, now, from being ready for prime time. :)