|
You cannot affect movement (setpoint) or visibility changes (show/hide) on secure frames in-combat.
You'd need to use a secure header to control visibility (within the macro system options constraints).
But it looks to me that your problem has a much easier solution.
If your buttons that you are trying to attach to your personal resource display are not meant to be clickable to cast but instead just show cooldown and such information about your abilities, you do not need to have them inherit secure templates `SecureActionButtonTemplate` and you'd sidestep the whole problem.
|