When using macros, it's difficult to flip between Action Bars, as, once you land on a given bar, there is no flip back option short mousing or keying back. The smartest way to handle them is to build your macros and place the needed actions directly below the Macros on the bar itself.
Example: Slot 1: Macro: Target <name of player/mob needed>
Run Shortcut 11 (heal/magic attack/melee attack)
Slot 11: Skill needed to perform the above action. (heal/magic attack/melee attack)
By building a bar with just your macros, you can perform many more actions smoothly without having to flip bars constantly. This means you don't always get the neat organization you might be looking for, but it makes macro implementation much easier. I, personally, kept all of my Foraging, Melee and Magic on separate bars, in addition to building special bars for things like NPC boss hunting and running Occupations. NPC hunting and Occ running require multiple skills that would be otherwise segregated to be at my fingertips, so I built those bars with everything I needed in one place.
I realize that this doesn't really solve the problem you're suggesting a fix for, but it's a work around til your idea is implemented.
Hope this helps. :D
Example: Slot 1: Macro: Target <name of player/mob needed>
Run Shortcut 11 (heal/magic attack/melee attack)
Slot 11: Skill needed to perform the above action. (heal/magic attack/melee attack)
By building a bar with just your macros, you can perform many more actions smoothly without having to flip bars constantly. This means you don't always get the neat organization you might be looking for, but it makes macro implementation much easier. I, personally, kept all of my Foraging, Melee and Magic on separate bars, in addition to building special bars for things like NPC boss hunting and running Occupations. NPC hunting and Occ running require multiple skills that would be otherwise segregated to be at my fingertips, so I built those bars with everything I needed in one place.
I realize that this doesn't really solve the problem you're suggesting a fix for, but it's a work around til your idea is implemented.
Hope this helps. :D