Kewl.
I'm working on this too. Tonight I am going to set up a cron job to run the
$ xmodmap -e 'keycode 115=F13' or just get it run on startup perhaps. I'll
see if KDE is losing the F13 map in its keybindings or if it is the xmodmap
that is being reset when X starts that way. If it's KDE's settings, I'll
figure out a way to automate binding F13 to KLauncher on the startup of KDE.
Thanks a lot,
Ravenhall
--- "No! There are no significant bugs in our released software that any
significant number of users want fixed. If you really think there's a bug
you should report a bug. Maybe you're not using it properly. Have you ever
considered that?"
- Bill Gates on MS products - German weekly magazine FOCUS (nr.43, October
23,1995, pages 206-212), www.cantrip.org/nobugs.html
_______________________
>I've been getting close but not quite there yet. Basically, you can do the
>following:
> $ xmodmap -e 'keycode 115=F13'
> Go to the KDE Control Center and change the global key bindings to pop up
>the launcher from Alt-F1 to F13 and hit Apply. This maps the left Windows
>key. You can also map the right Windows key (I think that was 116).
>
>What's not working for me yet is to get this to stick. Although the
>control
>center says the key is mapped to F13, it doesn't seem to be. I need to go
>into control center again after KDE starts and hit apply again. I haven't
>found the right spot to put the xmodmap command in yet.
>
>Cheers,
> .../Ed
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
