Another playground lost by accidentally pressing Reload. Please make the Playground survive a reload!
To server or to browser?
I was thinking just in the browser. We can save if/when weāre ready, the main thing is to not lose it.
Saving last āRunā or last edit? What if multiple playground open in the same browser?
I have to admit it happens to me from time to time ā¦ and I canāt say I like it when it happens ā¦ Of course, itās my bad. And I also took some countermeasures - by copying everything to my notepad/textedit when making long or important PGs. Still, not the best CXā¦ and when I think of it, all OS and nearly all games I play ask me twice if āIām sureā¦ā when attempting to quit or return to menu. To a point where it eventually becomes annoying So, I guess there are pros and consā¦ Canāt just take the user by the hand and disregard all orders like you would do with a 4-years old ā¦ But overall, there might be some sort of compromise to be foundā¦so let me actually upvote this ā¦ providing there would be a good solution for it
You can toggle the safemode property in the options:
It will prompt you to confirm you want to exit on page reload:
When you exit and reopen the tab, the option is remembered.
LoL. Completely forgot about this. This solutionās good enough for me Can I take back my vote?
I think safe mode should be the default, this would fix the issue and people who want to live dangerously can always revert to unsafe (but then they acknowledge that they are in unsafe mode). Not the other way around
Iām half/half on this (as stated in my last post). Yes, the trend today is to take the user by the hand (and more ). But I donāt really like itā¦except when I do
I was also thinking from the perspective of a new developer. Writing stuff in the playground will probably be one of the first experience when learning BabylonJS.
You only get one shot at making a good first impression, and losing your work because the default setting is silently set to unsafe is not a good first impression.
At least, there should be some warning somewhere visible that shows āauto save on/offā instead of burrying it in a menu.
I didnāt know it was a feature and I used the PG for more than 5 years now (but then I tend to miss very obvous stuff sometimes )
Haha Thatās conforting to hear. Where I actually knew about it and next thing that happenedā¦ I forgot
Yes. So much is true. And I agree that one of the unique advantages of the PG is to commit new users. With this, youāve just added 10% to my half/half. Now Iām 60/40 (in favor of the default set to āsafeā)
How about we observe the amount of time/number of changes in the editor, then it always pops up with the confirmation if > xš wonāt need the Safe mode button then. Or change it for āAlways warn of unsaved changesā