Summary | Shortlog | Commit | Commitdiff | Tree |

Don't apply wrong-spec bindings

Author	James Whitehead II <jnwhiteh@gmail.com>
Author date	2012-09-06 07:32:54
Author local date	2012-09-06 09:32:54 +0200
Committer	James Whitehead II <jnwhiteh@gmail.com>
Committer date	2012-09-06 07:32:54
Committer local date	2012-09-06 09:32:54 +0200
Commit	4dbc7afcc5d4ba8a0223315429d3b7ec75c4753d
Tree	24e3b5795f88cda66204eb6d0f95a3e7a39fc674
Parent	690e0109e1d5dabd4d4d3b9f5bb1c3f56b8879e4

Don't apply wrong-spec bindings

Previously, if you were in your primary spec and you had a spell that
was bound to secondary spec only, the binding would still be active
(although it would not do anything). Simple test:

  1. Bind 'moonfire' to 1 on hovercast,secspec
  2. Verify it works
  3. Change to primary spec
  4. You will be unable to use your '1' normal binding