This repository was archived by the owner on Dec 20, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Logging
Ángel Serrano edited this page Apr 3, 2014
·
1 revision
To print log messages, we use libgdx logging.
Gdx.app.log("MyTag", "my informative message");
Gdx.app.error("MyTag", "my error message", exception);
Gdx.app.debug("MyTag", "my debug message");We consider the following logging level definitions:
- serious stuff that should not be ignored:
error(important file not found, load failed, ...) - informative, low-frequency events ("game loaded") that indicate state changes should use
info(Gdx.app.log) - everything else:
debug
eAdventure - eUCM research group
- Setting up a Development Environment
- Contributing Guidelines
- Build Process
- Project structure
- Schema
-
Engine
- Files paths and FileResolver
- Binding Schema elements with Engine elements
- Managing the game view through Layers
- Game loop and scene management
- IO
- File Resolver
- Assets: Converting schema objects to engine objects
- Engine Objects
- Actors
- Effects
- Testing the engine
- Editor
- Remote communication
- Release Process
- Other documentation