Open collectivenectar opened 2 years ago
Possibly solution I'm testing is a simple global.carousel_choice.invert() after the last card has been chosen in the spread. This should be applicable to the global.livedeck array as well, I can test this once I've got all the cards entered into the array, as testing it right now would be a bit impractical. Considering this mostly solved for now but leaving open as a reminder.
The carousel position values run opposite what you might think, and it may cause issues showing the correct cards consistently. This needs testing, and confirmation.
Confirm it does/doesn't have an effect on:
Choose your cards(hidden chosen order vs display order) see your cards(chosen order vs displayed order) the deck(original deck order) user history(loading)
Figure out if I need to redesign just the way the carousel_position is calculated, or if I can just do some quick array ordering to fix this.