Since I've never been able to make 'chase pointers' work (not knowing that it only worked on self) I don't know exactly what it does, but I imagine it's something along the lines of Avi's PointerExplorer. Perhaps it would be better to drop the 'chase pointers' feature and look at including something built from PointerExplorer (I know it still has a few issues) instead? It has the advantage of only opening one level at a time so it doesn't infinitely recurse.
Actually, reading Andreas' comment again, maybe recursion wasn't the problem he was referring to? Anyway, something to consider perhaps.
But if nothing else, it seems like it would be nice to make 'chase pointers' not show up for anything except self.
Andreas Raab wrote:
Seems like this qualifies as a bug, especially since the similar 'objects pointing to this value' works on any variable selected in the inspector. Ought to be fixable, I'd think.
This might be harder than you think - I remember briefly looking at this problem way, way back when I first encountered it and not being able to come up with a good solution - the issue is that you do NOT want to include the inspector in the reference chain to the object and that is not exactly trivial to do. But if you can find a way I'll be forever grateful ;-)
Cheers,
- Andreas