To be sure what does the processing of the click, put a message or something else that gives you a sign "Hey here we are!", immediatly after the "IF".
Normally, all the "IF" branches should work in this code. So i suspect there is another thing what leads you to think a branch doesn't work.

Hi JGGamer!

You now have the events all in a group and value is true for some and never for the other.
Try separating the events
Get rid of the else in the function
If it's over do this...
If it's clicked do this

I tried everything I could think of, as I said before. Using case gives the same result - no change.
Thanks for trying fellows, but I think we had better close this thread. I think I'll try a workaround instead of using this feature. Thanks

This is strange ... There have to be a solution for this ^^ Give us the whole source of the panel definition an so on, pls. Then we could test your code and debugg with our own methods to tell you where is the catch. Do you have set all three function-pointers functionOn, functionOff, functionOver in the button definition?

I don't believe the problem lies with the code, because the animation works with the mouse over, but not with the mouse click, so I believe it has to do with the animation. I prefer not to go through this however, because I observed that it does not work to my liking. If I move the mouse over the button and the animation starts, if I quickly move the mouse off the button, the animation if left in mid-action, and does not complete as it should. This I don't want, so I will find an alternative to this. Please don't bother with it. Thanks for the interest in helping.

My experiences show that, in such cases 100% the mistake is in the code. The remaining 0,1% in the engine.
But if you wish, i don't try more.