What is best practice in handling movement from screen to screen in midlet?
My teacher at university wasn't able to explain this to me, could be due to that he chuck whole 300+ lines in one file.
Secondly none of the books or tutorials that I read so far went on discussing this.
So here is how I do it and I would like to know if my approach is correct and if not I would like to know how to handle this correctly.
In my opinion this better solution then sending instance of Displayable argument to next class.
posted 6 years ago
In displayable classes, I'll get a instance of this midlet through constructor. And i'll call getDisplay() where ever i need...