Menu Not Affecting Currently Running Spread Scenes - Related to Lifecycle?

[collectivenectar]

I haven't even thought to build for this, but I need to start thinking of it now, so here's the issue for it.

I need to have it so the user can pull cards, leave the scene to look at the guide or something else, and then be able to go back to the scene without anything changing. I'll need something that can break the process down into stages, with the ability to continue where one has left off. This will mean likely a rewrite of the current api for all scenes in the draw cards process.

Features:

• As soon as a spread is chosen, begin saving the progress. Once a spread has been chosen, create an autosave file and give it a name that is auto generated
• Allow the user to navigate to other sections of the app without losing their spot - This may or may not mean saving and loading the scene each time they do this, but I should expect to have at least one function doing this, so I might as well write for longevity.
• Note when a reading was incomplete or unfinished in the save file itself, so the system knows the difference
• Write better api for populating incomplete reading data into scenes
  • This means working out a better way to modify the database to change what cards are in global.carousel_choice, any other global vars related to current focus/center card info etc, and how many cards are currently displayed as chosen in accumulative layout tscn.

This could open an opportunity for me to build in the undo button for chosen cards, so I might as well do it while I'm at it.

[collectivenectar]

Oh I also forgot, added complexity being that if I removed the 'X' for leaving the show your cards.tscn, how does the system know which scene I am in and what to do about it? This needs to be addressed. At each step when a card is chosen, I can save, but I still need to manage a save for lifecycle issues, so I might as well figure this out one way or another. Consider signals? Or signal groups?

[collectivenectar]

Also realized I'll need to save states for the deck carousel and the guide as well, but it won't be as complex.

For the carousel, just the carousel position, and maybe an autosave for user notes For the guide, just the page and scroll position in the book, and maybe an autosave for user notes. For user history, unlikely that I'll need to store anything, except maybe scroll position if it turns out to be annoying.