ClassBinding

THIS ADDON HAS BEEN DISCONTINUED

Since Blizzard added per-character key binding, this addon became mostly irrelevent. Just enable the option at the top of the keybindings interface pane. Though it did have a few features that Blizzard's method does not have (including to be able to save per class, and to save/load bindings from other classes or characters), Blizzard's method is sufficient for the main purpose. Using it means I never did have to figure out just what they changed in the API that broke being able to ensure that the bindings cache got written at the right times.

=====================

Old description, for historic reference: This add-on saves the key binding setup per each class you play, so that you can have one set of bindings for a rogue, one for a paladin, one for a shaman, et cetera, and all will be seamlessly saved and loaded as you switch around between your characters. For version 2.0, per-character bindings were added. Here is the command list:

      /cb save <char|class>
       /cb load <char|class>
      /cb delete <char|class>
      /cb unique {on, off} (but no "toggle")
       /cb alwaysunique {on, off}
       /cb status (shows status of unique)

By default, a character will get and store bindings for the entire class unless unique is on. When unique is on, it will only affect that character's bindings and not the class. If you turn on alwaysunique, then the default becomes to always save bindings per character. The command line tries to be flexible in recognizing the difference between a character name from a class name, but you can potentially run into a problem if you have a character named after a class but want to keep the bindings separate, such as if you had a warrior named Priest. Class names have all been localized for German and French, but in some tricky circumstances you might need to disambiguate a class name from a character name and will then need to use the internal format of a per-character name. Internally it is stored as @realm:name, such as @Kilrogg:Woofiest, with any spaces in the realm's name changed to the "_" (underscore) character. When turning unique on, the current bindings for the character become isolated from the bindings for the class. When turning unique from on to off, the current bindings are forgotten and the ones from the class are loaded. If you wanted the current bindings to be the new default bindings for the class, you would need to first save the bindings to the class. This is also true when turning off alwaysunique -- turning off alwaysunique implicitly turns off unique for the character you are currently playing, but leaves other characters alone. Using "save" to a character automatically turns on unique for the character. This is because unique is not tracked as a separate variable, it is just the presence or absence of the @realm:name in the table. When doing a save to a character name without using the @realm:name form, it will show up in the status command as "Unknown Server" until you log into the character. If you then see the character's name twice in the status list (one with unknown server, one with a server) then the one with the unknown server will overwrite the one with the known server when you log in; this is intentional, under the presumption you were trying to replace the character's bindings. Use the full internal format if you want different behaviour. TODO: Graphic configuration pane, for use with myAddons