ISBoxer: null exception when exporting if named wow macro has no keybind

[Ughmahedhurtz]

DESCRIPTION

ISBoxer generates a null reference exception when exporting if you add a named wow macro to a mapped key but the named macro does not have a keybind set.

System.NullReferenceException: Object reference not set to an instance of an object
at ISBoxer_Toolkit.Configs.KeyMaps.Step.GenerateInner SpaceSettings(Set set, MappedKey mappedkey, KeyMap keymap)
at ISBoxer_Toolkit.Configs.KeyMaps.MappedKey.Generate InnerSpaceSettings(KeyMap keymap)
at ISBoxer_Toolkit.Configs.Keymaps.Keymap.GenerateInn erSpaceSettings()
at ISBoxer_Toolkit.Configs.ISBoxerToolkitProfile.Gene rateKeyMapperSettings()
at ISBoxer_Toolkit.Pages.Leaf.InnerSpacePage.ExportTo InnerSpace(Boolean showSuccess)

STEPS TO REPRODUCE



Create new Game Helper -> World of Warcraft -> Quick Setup 38 -> New WoW Macro
Add macro text
Leave "Key Combination" empty/unset
Key Maps -> General -> <some mapped key> -> Steps -> Actions -> Keystroke Actions -> New Named World of Warcraft Macro Action
WoW Macro -> set to the new wow macro created in steps 1-3 above.
CTRL+E to publish
Export to Inner Space failed.


HOW OFTEN CAN THE PROBLEM BE REPEATED?

100% of the time

Version found in: ISBoxer Toolkit 40.5.1130.1, also happens in 40.5.1206.2.

EXPECTED BEHAVIOR

Expected behavior is a prompt that the user is trying to directly call a named macro that does not have a valid keybind set.

IS THERE A WORKAROUND FOR THE PROBLEM?

None found. Setting the macro's /click name and calling it via /click in another named macro does not generate an exception.

[Lax]

Thanks, fixing that now.

The bug you're reporting is a bug in the part that is supposed to detect that you're giving it a WoW Macro with no key combination, and tell you that you're doing it wrong.

Your two choices are indeed to either a) give it a Key Combination, or b) assign a /Click name and use the /click command from another WoW Macro.