Shared spellIDs and specs

[Duugu]

[e]
Nevermind. Solved the problem with using spellnames instead of spellIDs.

Still would love to hear whats wrong with using spellIDs. But that would be 'nice to have' only.

------------------------------------------------------------------------------------------------------------------------------------


I'm trying to fix a problem with my secure action buttons and spells on different specs.

Problem:

Take a priest with first spec Disc and second spec Shadow. Let the spec Shadow be enabled and the Shadowform be enabled.

If I drag the spell Mindflay from the spellbook onto a Bizzard button, and then cast Mindflay via this button, everything is ok.
If I drag Mindflay from the spellbook onto one of my secure buttons, and then cast Mindflay via my secure button, then Mindflay IS casted, BUT the Shadowform is cancelled. oO

Cause:

After some tests I figured out, that dragging Mindflay from the spellbook onto my secure button actually passes somewhat unexpected arguments.

The secure button receives the following data with "OnReceiveDrag": kind, value, subtype, extra = "spell", 27, "spell", 585

I can manually verify that Mindflay is indeed shown at index number 27 in the spellbook.
But, the spellID of Mindflay is not 585. The spellID of Mindflay is 15407. 585 is the spellID of Smite.

GetSpellBookItemName(27, BOOKTYPE) returns "Mindflay", ""
GetSpellBookItemInfo(27, BOOKTYPE_SPELL) returns "SPELL", 585

I'm guessing that the cancelled Shadowform is somehow related to the spellID 585 Smite - which is a holy spell and should indeed cancle the Shadowform on use.

Question:

I know that Blizzard replaces spells/ids based on the current spec. So, receiving 585 is probably ok and intended – but if 585 with Shadow spec is actually Mindflay, why does casting it via my button (with action="spell" and value=585) breaks the Shadowform???
Am I doing something wrong? Or is this just a bug?

On a side note: setting the secure action button manually to action="spell" and value=15407 (the original spellID of Mindfay) does not work at all - which is no real surprise as Mindflay seems to be 585 in this scenario.