Fri Jan 08, 2010 3:47 am
Keybind Conflicts
First of all i would like to humbly thank Mr. Lax for empowering us to all be better gamers. Most of these proposed solutions have probably already been thought of so just think of this as a yellow sticky pad on your wall.
I have 5 Propositions that would help with key conflicts.
1. Produce a key list or "no fly zone" to stay away from when assigning keys to World of Warcraft Key binds.
2. Create a config file for text editors that would highlight and color code the important aspects of our profile.
3. Make the built in key conflict system adapt to identify keys used for FTL and warn of any combination of keys associated with it.
4. Make the built in key conflict system tell you where that conflict are.
5. Populate a list of what Key combinations are free, used for macros, used for FTL actions.
-Produce a key list or "no fly zone" to stay away from when assigning keys to World of Warcraft Key binds.
This would be the simplest way to fix the problem. Time and time again "key combination" conflicts has been holding back my creativity. I tweak and add new map sets almost daily. It has been brought to my attention that FTL binds are the main culprit. In my key binds the only FTL actions are in my "Control, General, General, and Targeting" Mapsets. With half of those mapsets produced by default it would be wonderful If we could publish a default "no fly zone", or keys that should not be touched. This has been addrssed. (see below) but only the F11 has been listed.
http://isboxer.com/index.php/guides/31- ... and-follow
examples:
F11 for follow actions
Backspace = assist actions
-Create a config file for text editors that would highlight and color code the important aspects of our profile.
The second and less user friendly tool we could use to weed out conflicts is a code editor like CoolEdit. It can be fed a config file that highlights certain keywords. "Ctrl" for example or "Num Del". This way we can at a glance quickly scroll down the pages, upon pages of macro's and key binds instead of fishing through the GUI drop down tree's.
example:
http://en.wikipedia.org/wiki/File:UE32.png
Make the built in key conflict system learn to identify keys used for FTL and warn of any combination of keys associated with it.
example:
if F11 was assigned to follow FTL by default then... a warning flag should go up in the conflict tool if someone tries to bind ctrl-F11 to say,..... Greater Heal.
- Make the built in key conflict system tell you where that conflict are
Currently The tool will only tell you how many other macros are using that same key bind. It doesnt tell you what Key Map(Tree) or Maped Key(Branch). This make hunting down the other bad difficult. With the fastest solution just to simply dig for another key combination that is not used.
-Populate a list of what Key combination's are free/used
This way we can at a glance plan out how we are going to spend those keys. list red keys as used and unused keys as green. and FTL keys as yellow. or whatever. We are visual creatures.
I'm not a programer so i cant help create these tools. I can tell you what the average users frustrations would come from. These are the things I have thought up that might alleviate the problems the profiler has at this time. I understand We are all Pioneers and years from now we will all look back at at this and laugh.
I have 5 Propositions that would help with key conflicts.
1. Produce a key list or "no fly zone" to stay away from when assigning keys to World of Warcraft Key binds.
2. Create a config file for text editors that would highlight and color code the important aspects of our profile.
3. Make the built in key conflict system adapt to identify keys used for FTL and warn of any combination of keys associated with it.
4. Make the built in key conflict system tell you where that conflict are.
5. Populate a list of what Key combinations are free, used for macros, used for FTL actions.
-Produce a key list or "no fly zone" to stay away from when assigning keys to World of Warcraft Key binds.
This would be the simplest way to fix the problem. Time and time again "key combination" conflicts has been holding back my creativity. I tweak and add new map sets almost daily. It has been brought to my attention that FTL binds are the main culprit. In my key binds the only FTL actions are in my "Control, General, General, and Targeting" Mapsets. With half of those mapsets produced by default it would be wonderful If we could publish a default "no fly zone", or keys that should not be touched. This has been addrssed. (see below) but only the F11 has been listed.
http://isboxer.com/index.php/guides/31- ... and-follow
examples:
F11 for follow actions
Backspace = assist actions
-Create a config file for text editors that would highlight and color code the important aspects of our profile.
The second and less user friendly tool we could use to weed out conflicts is a code editor like CoolEdit. It can be fed a config file that highlights certain keywords. "Ctrl" for example or "Num Del". This way we can at a glance quickly scroll down the pages, upon pages of macro's and key binds instead of fishing through the GUI drop down tree's.
example:
http://en.wikipedia.org/wiki/File:UE32.png
Make the built in key conflict system learn to identify keys used for FTL and warn of any combination of keys associated with it.
example:
if F11 was assigned to follow FTL by default then... a warning flag should go up in the conflict tool if someone tries to bind ctrl-F11 to say,..... Greater Heal.
- Make the built in key conflict system tell you where that conflict are
Currently The tool will only tell you how many other macros are using that same key bind. It doesnt tell you what Key Map(Tree) or Maped Key(Branch). This make hunting down the other bad difficult. With the fastest solution just to simply dig for another key combination that is not used.
-Populate a list of what Key combination's are free/used
This way we can at a glance plan out how we are going to spend those keys. list red keys as used and unused keys as green. and FTL keys as yellow. or whatever. We are visual creatures.
I'm not a programer so i cant help create these tools. I can tell you what the average users frustrations would come from. These are the things I have thought up that might alleviate the problems the profiler has at this time. I understand We are all Pioneers and years from now we will all look back at at this and laugh.
