I stand corrected! Ironic since one of my pet hates is people posting theoretical stuff as what looks like genuine code, saying "I don't know if it'll work...." when it's pretty easy to just try!

My excuse - and theirs too, I expect - is that I was at work Anyway, you're right. I just tried it myself, and it no longer falls through. I'm certain it used to.

That means you're back to separate buttons I guess.

Removing "not ready" and similar messages is a bit academic now I guess, but the answer is to use "/script UIErrorsFrame:Clear()" at the end of the macro.