I'd like to preface this request by saying that I understand, to a degree, the logic behind limiting macro functionality, even if I don't agree with it, but this particular request isn't so much about expanding the functionality of macros so much as implementing something that feels like it should be possible to already based on the way they already work.
I have relatively small hands, and play on the mouse and keyboard; as a result, I have a tricky time pressing keys beyond 5 without moving my hand and thus screwing up my ability to move around in the process. To help counteract this issue, I've taken great efforts to streamline my hotbar in any way possible to reduce the number of buttons I have to press, by utilizing macros to flip through 'combo pages'.
Functionally speaking, there's nothing particularly wrong with this because I can get it to work reasonably well, but in the process of tweaking it until it was usable, I came up across a frequent annoyance; there is no command to place a macro from your User Macros onto your hotbar.
This strikes me as strange; why are Just macros unable to be commanded into the hotbar? there are a vast array of /hotbar commands for putting just about every other action, pet action, emote, item, or anything else you can think of on the hotbar, so why are macros specifically left out? Let me show you what I mean, using Dark Knight as an example.
Look at this mess. See what I have to do in order to simply make a couple of buttons move around? To clarify, each step of DRK's basic combos are macroed to change the page to another page that contains the next step of the combo. It works, but it's bulky and an annoyingly roundabout way of achieving something that Should be simple; replacing the buttons on my hotbar with the next step of the combo, to condense the entire thing down into the space of two or three keys.
If there was a command that could simply assign a macro to a hotbar slot, there would be no need to even deal with this page-rotating nonsense. Something like, say,
where [1] is the number of the macro assigned on the User Macro menu, [2] is the number of the hotbar, and [3] is the number of the slot, would make it much easier to replace one button with another button that is also capable of replacing itself. Given that you can already, as I've stated, use a text command to manipulate the hotbar in just about any other way you can imagine, the fact that you can't do so with macros feels egregiously intentional, and for no other reason than explicitly to limit functionality.Code:/hotbar macro [1] [2] [3]