You should have mentioned your predicament in the first place. Most people will read your posts with standard setups in general. I finally understand why you want to set up your bars the way you want to set it, even though I still can't envision what your setup is like.
Still, going by your post, I'm not entirely sure if you're actually aware that if you turn off crossbar or hotbar sharing, each class and job has their own full sets. Unless you turn on cross bar sharing, even gladiator and paladin has their own 8 crossbar sets and 10 hotbar sets. If we do not count the combat classes and count their combat jobs instead, we have 9 combat jobs and 11 craft/gather classes. With zero set sharing, you have 8 cross bar sets...times 20. Or 10 hot bar sets times 20. Again, if you dont actually make your cross bars share between jobs and classes, I dont see how you'd be lacking in slots. Hell, you should be able to make lots of duplicates with slight changes and not run out of space.
As for wanting to eliminate certain buttons to heavily simplify your actions, I don't think it'll work 100% of the time so I don't think it's worth it. Let's just use cleric stance for example. /ac cleric stance; /chotbar set ___. You accidentally pressed that macro way too early and you were still casting cure. The game will perform the /chotbar set but ignore the /ac cleric stance because you have not fnished casting. You would have switched into your damage dealing skillset without actually going into cleric stance. We can add a /wait in between but that still doesnt completely eliminate the risk of mistake. Same with announce macros for things like silence and stuns and provokes. Mashing it would add spam to party chat and annoying your party members but adding a /wait might completely eliminate your announcement because you could have pressed another macro before the announce happens, interrupting the announce macro. It's part of what I dont like about the macro system; you cant specify the macro to only continue if the previous action succeeded as long as the next lines aren't another /ac.
Another flaw with macro is that you can't queue your actions with it. The macro will only start after you are available and not stuck doing another action while non macro skills can be queued slightly before your first spell ends. It's why I try to avoid using macro on my basic healing spells because if I need to chain cast it, I'd technically be going slightly slower than non macro healing.

Originally Posted by
ariaandkia
To really understand the issue, you really need to play as a scholar where you need to place your pet and sometimes you need to control it manually, especially when you need skills to activate in a specific order to get a nice combo going, but also need it to happen fast (thus you can't simply macro it)
On the contrary, I think place and heel can be macrod into one.
Code:
/micon "Place" pet Eos
/pac "Place" <me>
/pac "Heel" <me>
This is what I use for my pet control. When you press this macro, the targeting reticule will pop up and your pet (any, eos line is for the icon) will return to you. Pressing confirm after that will make your pet run towards your target, pressing cancel will cancel the place command and your pet should already be returning to you. Press the macro and then confirm/cancel fast enough, your pet should either be flying straight to the target location or returning to your side. I usually use this on hold mode but toggle mode also works.
I use this for all my pets and I have different needs depending on the pet summoned eos/selene/titan/garuda/etc so I add additional commands on this macro to reset it's aggro behavior and pick sic/obey on other macros I'm using.