Tip: Performance optimization when using WeakRefs

I just blogged about using WeakRefs more efficiently. Who knows, maybe even the Xojo IDE could benefit from this if it isn’t doing this already :wink:


Nice tips. I’ll have to keep this in mind next time I do something like this.

That’s a great tip.

The new framework uses a factory method to return a WeakRef. I wonder if there would be an efficient way for it to return the same WeakRef for the same object? I turned this into a feature request to find out:


Well, we often put WeakRef at parent to keep the number low.
Should work same with old and new framework.