- Joined
- Sep 26, 2009
- Messages
- 9,534
I love the pic! That is some gold-tier flavor for this resource.
I would, however, provide feedback that the amount of boilerplate required for users seems too much. I've not worked with
Correct me if I'm wrong with this, but I'm thinking that the immutable properties of a
If that's the case, you have the ability to do some automation with how the recycling works, by hooking the
Given your example of how to use this, I would think that
I would, however, provide feedback that the amount of boilerplate required for users seems too much. I've not worked with
frame
s before, aside from treating them simply as any other handle
in systems like Table
.Correct me if I'm wrong with this, but I'm thinking that the immutable properties of a
frame
are defined simply via the BlzCreateFrame...
calls?If that's the case, you have the ability to do some automation with how the recycling works, by hooking the
BlzCreateFrame...
functions, storing the arguments to a table, also hooking the BlzDestroyFrame
function to flag when it's to be released. Once the user calls one of the BlzCreateFrame...
functions, as long as the args are exactly the same, and a recycled frame
coincides with that same argument list (checking if all args are equal) then go ahead and provide that frame
to the user.Given your example of how to use this, I would think that
BlzGetOriginFrame
is always returning the exact same frame
, correct? If not, then that's another reason to discard this feedback.