https://linen.dev logo
Join Discord
Powered by
# ceramic
  • a
    ohhh, you mean just not used it lol?
  • a
    @billowy-waiter-28954I just tried switching back to a previous scene set as 
    main
    but it seems like ceramic destroys previous scene instances
  • a
    is this behaviour togglable?
  • a
    maybe i'm misunderstanding how to handle scene switching in ceramic 🤔
  • f
  • a
    huh, guess i don't understand how the scene system is meant to work
  • f
    what are you trying to do?
  • a
    just change scenes and keep the state of the old scene
  • b
    The idea of assigning a main scene (with 
    app.scenes.main = new SomeScene()
    ) is to manage resources and memory
  • b
    So yeah, if you assign a new main scene, the previous one will fade out and be destroyed
  • b
    So if you want to "go back" to that scene
  • b
    you need to instanciate a new one
  • b
    (which is fine)
  • f
    or if you're changing scenes with the intention of going back soon, you should use a different layer and make the current one inactive?
  • b
    If you want to keep a scene around all the time, you can do it, you simply need to assign it to another slot with 
    app.scenes.set('slotname', myScene);
  • b
    (and if you assign another scene to the 
    slotname
    slot, then same rule applies as when assigning another scene to `main`: the previous scene fades out and is destroyed)
  • a
    This seems like a different thing though, because a secondary scene isn't really 'secondary'. Its more like a scene group. I'm mostly trying to understand the intended workflow... Oh! I think I get what you mean
  • a
    Copy code
    hx
...set('a', scene_a);
...set('b', scene_b);

scenes.main = scene_a;

buttonClick() {
  scenes.main = scene_b;
}
  • a
    this would cause the scene's to persist, right?
  • a
    I don't get this though, because adding a secondary scene is rendered onto the main scene
  • a
    so it isn't really the same thing
  • f
    or would it be more like this?
    Copy code
    hx
...set('a', scene_a);
...set('b', scene_b);
scene_a.active = true;
scene_b.active = false;
buttonClick() {
  scene_a.active = false;
  scene_b.active = true;
}
  • b
    No you should not assign the same scene to 
    main
    and to another slot with 
    set('blah', ...)
  • b
    Basically, doing 
    app.scenes.main = ...
    is the same as doing 
    app.scenes.set('main', ...)
  • b
    Yes this seems more correct if you want to keep your scenes in memory
  • a
    ahah, that works
  • a
    so ceramic's flow is essentially. Everything is handled in the 
    MainScene
  • a
    (more or less)
  • f
    hey, that wasn't so hard
  • a
1...626364...124Latest