(libgdx官方文档)日志工具

Logging

Table of Contents

a note from the translation

Wiki Style Guide

• Developer's Guide
  • Introduction
  • Goals & Features
  • Community & Support
  • Contributing
  • Games Built with Libgdx
  • Prerequisites
  • Gradle Project Setup, Running, Debugging and Packaging
  • Project Setup, Running & Debugging
    • Manual Project Setup
    • Maven Integration
    • Using libgdx with IntelliJ IDEA
    • Using libgdx with Android Studio
    • RoboVM Notes
    • GWT Notes
    • GWT Super Dev Mode
  • Third Party Services
    • AdMob in Libgdx
    • Swarm in Libgdx
    • NextPeer in Libgdx
    • Google Play Game Services in LibGDX
  • Working from Source
    • Running Demos & Tests
    • Building libgdx from Source
  • Using libgdx with other JVM languages
    • Using libgdx with Clojure
    • Using libgdx with Python
    • Using libgdx with Scala
  • The Application Framework
    • The Life-Cycle
    • Modules Overview
    • Starter Classes & Configuration
    • Querying
    • Logging
    • Threading
    • Interfacing with Platform-specific Code
  • A Simple Game
    • Extending the Simple Game
  • File Handling
  • Networking
  • Preferences
  • Input Handling
    • Configuration & Querying
    • Mouse, Touch & Keyboard
      • Polling
      • Event Handling
    • Controllers
    • Gesture Detection
    • Simple Text Input
    • Accelerometer
    • Compass
    • Vibrator
    • Cursor Visibility & Catching
    • Back and Menu Key Catching
    • On-screen Keyboard
  • Memory Management
  • Audio
    • Sound Effects
    • Streaming Music
    • Playing PCM Audio
    • Recording PCM Audio
  • Graphics
    • Configuration & Querying Graphics ??
    • Fullscreen & VSync
    • Continuous & Non-Continuous Rendering
    • Clearing the Screen
    • Take a Screenshot
    • OpenGL ES Support
      • Configuration & Querying OpenGL ??
      • Direct Access ??
      • Utility Classes
        • Rendering Shapes
        • Textures & TextureRegions
        • Meshes
        • Shaders
        • Frame Buffer Objects
    • 2D Graphics
      • SpriteBatch, TextureRegions, and Sprite
      • 2D Animation
      • Clipping, with the use of ScissorStack
      • Orthographic camera
      • Mapping Touch Coordinates ??
      • NinePatches
      • Bitmap Fonts
        • Distance field fonts
      • Using TextureAtlases
      • Pixmaps
      • Packing Atlases Offline
      • Packing Atlases at Runtime
      • 2D Particle Effects
      • Tile Maps
      • scene2d
        • scene2d.ui
        • Skin
    • 3D Graphics
      • Quick Start
      • Models
      • Material and environment
      • 3D animations and skinning
      • Importing Blender models in LibGDX
      • Perspective Camera ??
      • Picking ??
  • Managing Your Assets
  • Utilities
    • Reading & Writing JSON
    • Reading & Writing XML
    • Collections
    • Reflection
    • jnigen
  • Math Utilities
    • Interpolation
    • Vectors, Matrices, Quaternions
    • Circles, Planes, Rays, etc.
    • Path interface & Splines
    • Bounding Volumes ??
    • Intersection & Overlap Testing ??
  • Physics
    • Box2D
    • Bullet Physics
  • Tools
    • Texture Packer
    • Hiero
    • Particle Editor
  • Extensions
    • gdx-audio
    • gdx-freetype
  • Deploying your Application
  • Building Libgdx ??
  • Known Issues
• Articles
  • Getting Help
  • External Tutorials
  • Bundling a JRE
  • Saved Game Serialization
• Deprecated (May be outdated)
  • Graphics Module
    • Screen & Viewport
  • Misc
    • Integrating Libgdx and the Device camera

The Application interface provides simple logging facilities that give granular control.

A message can be a normal info message, an error message with an optional exception or a debug message:

Gdx.app.log("MyTag", "my informative message");
Gdx.app.error("MyTag", "my error message", exception);
Gdx.app.debug("MyTag", "my error message");

Depending on the platform, the messages are logged to the console (desktop), LogCat (Android) or a GWT TextArea provided in the GwtApplicationConfiguration or created automatically (html5).

Logging can be limited to a specific logging level:

Gdx.app.setLogLevel(logLevel);

where logLevel can be one of the following values:

• Application.LOG_NONE: mutes all logging.
• Application.LOG_DEBUG: logs all messages.
• Application.LOG_ERROR: logs only error messages.
• Application.LOG_INFO: logs error and normal messages.

demo

package com.example.groupactiontest;

import com.badlogic.gdx.Application;
import com.badlogic.gdx.ApplicationListener;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.graphics.GL10;

public class MyGame implements ApplicationListener {

	@Override
	public void create() {
		
		Gdx.app.setLogLevel(Application.LOG_ERROR);//这时候使用Gdx对应的log工具来打log的时候就只能看到error级别及以上的了 
		//使用libgdx提供的打日志的方法写日志。还是在logcat中查看
		Gdx.app.log("MyTag", "my information message");
		Gdx.app.error("MyTag", "my error message...");
		Gdx.app.debug("MyTag", "my debug messgae");
		
	}

	@Override
	public void dispose() {
		// TODO Auto-generated method stub

	}

	@Override
	public void pause() {
		// TODO Auto-generated method stub

	}

	@Override
	public void render() {
		Gdx.gl.glClear(GL10.GL_COLOR_BUFFER_BIT);
	}

	@Override
	public void resize(int arg0, int arg1) {
		// TODO Auto-generated method stub

	}

	@Override
	public void resume() {
		// TODO Auto-generated method stub

	}

}

源码下载链接：

http://download.csdn.net/detail/caihongshijie6/7036095