Hi I’m using Nifty Gui in my JME3 game and I’m running it on android 4.4.2 on galaxy note 2. Everything is working fine. I have gui with 3 buttons to control the character in my tile-based game.
But for whatever reason when I turn the screen off with the power button and turn it on again the gui stops working. The game is still working, coz my character is moving (animating), but GUI buttons are not responding. I can’t even see color change when I click them. Please help me if you know the reason of this strange behaviour.
Should I reset the gui in onResume() method which is part of the Android Activity? How should I reset the gui? Remove it and add again? Should I read the XML again?
Some code from my application:
In simpleInitApp() I call loadNifty method:
public void loadNifty() {
NiftyJmeDisplay niftyDisplay = new NiftyJmeDisplay(assetManager, inputManager, audioRenderer, guiViewPort);
Nifty nifty = niftyDisplay.getNifty();
nifty.fromXml("Interface/nifty.xml", "start", new MyScreenController(p));
guiViewPort.addProcessor(niftyDisplay);
}
I pass the character reference to MyScreenController to call actions on the character when the user clicks a button.
In my opinion somehow GUI gets frozen after onPause() method. I read the console output very carefully and I found nothing suspicious. Only a warning about failing link of class Lde/lessvoid/nifty/ClipboardAWT and unable to access class java.awt.datatransfer.Clipboard.
I have also a warning about missing element control, but Im using a screen control class in my project, so I think this is not a big deal.
Does your MyScreenController extend AbstractAppState or is it stored in a private field?
one thing that happened to me before was that my screen controller was not stored anywhere and on resuming, the reference was gone. I solved it by either storing it as a private variable or another class or make it an app state and attach it to the state manager. That worked for me.
Hi. I implemented MyScreenController as AbstractAppState and it is stored as a private field in MyGame class (main game class extending SimpleApplication). But somehow I can’t get it working Even the easiest scenario where I:
turn on the game
switch off smarphone screen
turn screen on again
is not working. The previous touched button is highlighted and I can’t press any other button.
Have you reattached the state to the state manager when android is resuming the application?
public class MainActivity extends com.jme3.app.AndroidHarness {
private static final int MY_REQUEST_CODE = 123;
@Override
public void onCreate(Bundle arg0) {
Log.i("jme3", "onCreate");
super.onCreate(arg0);
this.addContentView(b, new LayoutParams(LayoutParams.WRAP_CONTENT, LayoutParams.WRAP_CONTENT));
}
@Override
protected void onResume() {
Log.i("jme3", "onResume");
super.onResume();
}
@Override
protected void onPause() {
Log.i("jme3", "onPause");
super.onPause();
}
@Override
protected void onStart() {
Log.i("jme3", "onStart");
super.onStart();
}
public MainActivity() {
Log.i("jme3", "Constructor");
// Set the application class to run
appClass = "com.jme3.core.MyGame";
// Try ConfigType.FASTEST; or ConfigType.LEGACY if you have problems
eglConfigType = ConfigType.BEST;
// Exit Dialog title & message
exitDialogTitle = "Quit game?";
exitDialogMessage = "Do you really want to quit the game?";
// Choose screen orientation
screenOrientation = ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE;
// Invert the MouseEvents X (default = true)
mouseEventsInvertX = true;
// Invert the MouseEvents Y (default = true)
mouseEventsInvertY = true;
}
}
Even with the simple start screen state i have problems with not working nifty gui after onPause and onResume. I have also a GameRunninState class which is very similar to StartScreen state class and a Player class used by the game.
Thanks for help
I think the problem is when you are detaching when you are using loadGameState and loadMenuState, Detaching an app state will also clean it up and remove it. even if you have a private variable that points to it.
You can do either of these:
Keep both always attached and have one “Active” at a time, you have one nifty scene controlled by an unique controller so this will be easy. If the game is of small scale, this solution should not be a problem. and with that active flag you can control what runs and whatnot. Here’s an example:
public void loadGameState() {
startState.setAvtive(false);
gameState.setActive(true);
currentState = gameState;
}
public void loadMenuState() {
gameState.setActive(true);
startState.setAvtive(false);
currentState = gameState;
}
on loadGameState and loadMenuState, you should initialize the new state to attach always and make null the one that is detached. This means you need to implement the cleanup method on StartScreenState and GameRunningState to avoid any bugs or crashes.
public void loadGameState() {
stateManager.detach(currentState);
currentState = new GameRunningState(this);
stateManager.attach(currentState);
}
public void loadMenuState() {
stateManager.detach(currentState);
currentState = new StartScreenState(this);
stateManager.attach(currentState);
}
But when turning the screen off no states are detached. In the simplest scenario I am not calling any of these methods. Just sitting on the start screen state and turning off then on the screen causes nifty gui to freeze. Game is running fine, I have already tested it. There are just problems with nifty gui.
I have tried already many things in android’s onResume method, such as reloading the state, recreating and reloading the state, reloading nifty etc, but nothing worked.
After onResume all my buttons do are warnings in console:
WARNING missing element/control with id [startButton#text] for requested control class [de.lessvoid.nifty.controls.TextField], but I’m getting them even when everything is working fine after the app is launched from start completely.
OK so after over a month I came to something. And quickly I’ve found similar topic on this forum:
The problem is that the setSimulateMouse boolean is resetting to true after android activity is resumed. I don’t know what is this happening, maybe InputManager is recreating or something. I don’t have much time to investigate that.
I am setting setSimulateMouse again to false after resuming activity and it’s working as expected, at least for the scenarios I’ve tested.
Even the easiest scenario where I: