Originally Posted by Resike
Yes but it runs after the server updated the values and vertified the item change, which takes much longer time, while the SetTexture runs in the middle of the change. At least that method seems to be smoother for me.
|
I don't understand. You can't update the texture until the server has made the change and sent the event to the client; the API returns won't be up to date until then. The default UI calls SetTexture in response to this event.
Originally Posted by Phanx
No, I mean, if two frames are registered for the same event, you can't guarantee which frame's event handler will run first. In practice they are usually run in the order registered, but it's technically undefined, like the order in which values are returned from pairs, so you shouldn't rely on it.
|
Maybe. Either way, it's not two different frames. The slot buttons (eg CharacterBackSlot) are the frames responsible for setting their own textures. Although come to think of it, not sure if some other event updated the texture as well.
Anyway, setting that field will be better of course.