add method within a Drag Controller works only on the first screen. about flame HOT 7 CLOSED

@luanpotter any thoughts on this?

from flame.

How are you handling your Game class and your PathSprite class? Can you share some more code on those bits? Basically if you are saving your data in a class that's going to get disposed when the user minimizes the app, it will be lost afterward. You can add it to the static context or inside a class that is going to be resilient towards that. However, if the user really closes (kills) your app, all runtime information is lost. The the only way to keep track of it using things like shared_preferences or sqlite.

from flame.

Hi sorry for the late reply

@override
void initState() {
    super.initState();

   _getGameStart();
 }
_getGameStart() async {

      Flame.audio.disableLog();
      Flame.audio.loadAll(['Calm.mp3']);
      Flame.images.loadAll(['star.png', 'starGlow.png', 'starCalm.png', 'path.png', 'starTrial.png']);

      var dimensions = await Flame.util.initialDimensions();
      gameController = new GameController( dimensions );

      gameWrapper = new GameWrapper( gameController );

  }
  GameController(this.dimenstions){
           initialize();
          _createStars();
         _initializeDragController();
   }

  void _initializeDragController() {
      PanGestureRecognizer gestureDetector = new PanGestureRecognizer( );

      Flame.util.addGestureRecognizer(
          gestureDetector
              ..onUpdate = (startDetails) => dragInput(startDetails.globalPosition));

      Flame.util.addGestureRecognizer(gestureDetector
            ..onEnd = (DragEndDetails d) => onUp());
  }

`

The PathSprite beside its initializer as a square with super.square there are no other functionalities

from flame.

@paulpmi , I'm assuming your GameWrapper is your implementation of the Game/BaseGame class. If you are saving that as a field of another component, it might get disposed, and then the constructor would be called again. I'd suggest creating a static variable to hold your instance, and only instantiate it once, as for the game state not to get lost. I'd suggest to add some logs in the constructor, where the points are all clear, and I suspect you shall find that it's being called again, because flutter disposes the widget tree when the app is minimized, including your game and the data. Saving it to a static context variable and making sure to instantiate it only once shall fix that problem :)

from flame.

Hey @paulpmi did @luanpotter advice fixed your problem?

from flame.

Busy month, sorry. Yes making the class that extends the BaseGame, in my case the Controller which is not shown, static fixes this problem. Thank you, I would have never thought of this !

from flame.

No problem, thanks for the feedback

from flame.