Timeline for LibGDX Game vs ApplicationAdapter

5 events

when toggle format	what		by	license	comment
May 3, 2016 at 13:54	comment	added	Czyzby		@VaheMuradyan, user already answered that: you don't have to clutter your code with empty method bodies. When you implement `ApplicationListener` directly, you have to provide all of the required methods, including ones that you don't need (like `pause()` or `resume()`, which aren't always used). `ApplicationAdapter` is out there for your convenience, so you don't have to keep empty methods around. It's a simple utility class, it adds no new functionalities - it just keeps your code cleaner (or shorter).
Jul 4, 2015 at 14:52	comment	added	Vahe Muradyan		so why they have created ApplicationAdapter if it doesn`t have any use?
Jul 4, 2015 at 14:14	comment	added	user3068350		You dont need to use ApplicationAdapter. Both ApplicationAdapter and Game implements the ApplicationListener interface. An adapter class is just a class that provides skeleton implementations for an interface so you dont have to clutter your code with empty method bodies. To use screens with Game you call setScreen and pass in a class that implements the Screen interface. You can make your screen classes take a Game object in the constructor so you can change screens within a screen.
Jul 4, 2015 at 13:57	comment	added	Vahe Muradyan		but when should I use ApplicationAdapter? And how shall I use screens here.
Jul 4, 2015 at 13:44	history	answered	user3068350	CC BY-SA 3.0