Depending on what you’re doing, you could also use reflection to access the field - you can then Mixin to the inner class, add an interface to it and expose the methods you need that way (you can mixin using the Mixin annotation like so).
Note that this has been requested on the Mixin github, with reflection as the stop-gap answer:
and a similar (though not the same) problem has been asked about on the forums
We don’t have much on what you’re trying to do so can’t really advise further (though not sure if I could anyway), but there are ways around it if you try hard enough!
Thank you. I will try to use reflection to solve this problem. But Im sure that it impact to performance.
I have no idea how to use interface mixin to solve.