You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked the repository for duplicate issues.
What feature do you want to see added?
An offline draft/cache function for Juxtaposition posts, where it automatically saves in cache your latest draft, for both text and drawing.
Why do you want to have this feature?
Because it's happened more than once that I'd have drawn very detailed pieces only for my wifi to temporarily cut out and thus blocking the entire app, forcing one to lose everything even though it had nothing to do with connection to the server. (Where a pop-up shows up saying to either reload or close Juxtaposition.)
TLDR: So it doesn't wipe out drafts when Internet connection cuts temporarily (especially knowing how... unreliable a 3DS' Internet connection can be).
Any other details to share? (OPTIONAL)
No response
The text was updated successfully, but these errors were encountered:
I'll approve this as something to look into, but I have my doubts at this becoming a thing. The browsers Miiverse uses on these consoles has very limited memory, and trying to store multiple draft posts may not be feasible
Checked Existing
What feature do you want to see added?
An offline draft/cache function for Juxtaposition posts, where it automatically saves in cache your latest draft, for both text and drawing.
Why do you want to have this feature?
Because it's happened more than once that I'd have drawn very detailed pieces only for my wifi to temporarily cut out and thus blocking the entire app, forcing one to lose everything even though it had nothing to do with connection to the server. (Where a pop-up shows up saying to either reload or close Juxtaposition.)
TLDR: So it doesn't wipe out drafts when Internet connection cuts temporarily (especially knowing how... unreliable a 3DS' Internet connection can be).
Any other details to share? (OPTIONAL)
No response
The text was updated successfully, but these errors were encountered: