Thank you for the help.
I just simply inserted the code you give me in the deactivated method, and looks like it works fine.
(BTW I have other views, I only need one of them to be destroyed after leaving it, I know it’s unusual )
I left activated() blank, as I need to call the super constructor anyway, because class extends AbstractView
I also wanted to ask, why do you have to give at least one parameter to the activated, deactivated method?
ViewHandler.activateView(Foo.class, this);
If i remove the the second reference to the object, my views doesn’t get to be activated. But if I understand it right, the activated/deactivated method uses that second parameter, but I don’t have any code in there. So it’s strange to me, that it doesn’t work properly without a second parameter. Although I might have done something wrong when removing all the this reference (maybe left it there somewhere…).
Anyway, I’m just asking this out of curiosity, and because someone might ask why do I have to use that parameter, then I could give him real answer instead of something made up
Your add-on was a great help in my project (still is, but I hope I’ll be finished soon).
I needed to extend the User class, but for me to do that, I would have to extend a whole other classes, so I used your source code, leave everything as it is, and comment the part I’ve made change to. Hope that’s OK?
Thanks for your help again, and for writing this great add-on! Very useful, I’ve use all modules except i18n, as so far I’ve only have one language supported