Originally Posted by Phanx
There's also no guarantee that your handler for that event will be run before the default UI's handler for the same event. Hooking the actual texture change is a better solution all around.
|
Before? You mean after? I'm hooking the button in question, so it will run afterwards, and I'm pretty sure this is the event that's used by the default UI to update the texture, so there should be no way it could fail. Seems less hacky than hooking SetTexture, to me.