0

I am making two screens A and B. Let's say they are screenA & screenB.

In screenA, I use setScreen(screenB) to pass the screenA to screenB.

In screenB, I have two methods two pass the screenB back to screenA.

Method 1

I create an imageButton called "Back". When I press the imageButton, it will use setScreen(screenA) to pass the screenB back to screen A.

Method 2

I use the soft key Keys.BACK to pass the screenB back to screenA.

My question s are:

1) Is method1 the same as method2?

2) Is my concept below correct?

Method1 Stack: screenA-->screenB on top-->Another ScreenA on top.

Mehod2 Stack: A-->screenB on top, then screenB is remove (if Keys.BACK is pressed) and back to A only.

If my concept is correct, will Method1 use more memory than Method2?

I hope you can understand my question and sorry for any troublesome.

Thanks for reply.

donfuxx
  • 11,277
  • 6
  • 44
  • 76
user1232250
  • 329
  • 3
  • 19

2 Answers2

2

I have the belief that setScreen() is not doing what you think is doing. setScreen() does not manipulate any stack. When you set the Screen the previous Screen is just removed and replaced from the new that you have added.

Let's say you do setScreen(ScreenA), then from ScreenA you do setScreen(ScreenB) -> ScreenA is removed and replaced by ScreenB. If you want to have a stack you can make your own. Usually I use a List and add each Screen on top and when back is pressed I pop it from List and I setScreen() the last Screen of the List.

On Keys.Back or Back button you would have the same logic.

And usually you would want to use this line in order to manipulate the back key with your logic.

Gdx.input.setCatchBackKey(true);
z3n105
  • 1,935
  • 1
  • 15
  • 14
0

LIBGDX provide you way to capture back button and there is an option to whether set it back to a screen, or just stop back button press by capturing it but not setting screen. This is a good practice because what if a user press soft key Back by mistake? you should check that. Another way by providing a back button on screen is what you want according to your project and user-friendliness. none of the method is memory consuming. its normal flow of app.

Aiman Batul
  • 144
  • 11