Hi, The code should actually be saved on disk every time you type. Please take a look at the files from play-cache. Could you confirm?
One bug is that the history is cached and not refreshed, so when you re-open a crashed page the image does not know that there is another file. This has to be changed. As for having the currently opened playgrounds in the dropdown, we chose it like that because when you open the dropdown you typically want to switch to something else than what exists right now in front of view. Thus showing the same entry again would provide little value. I believe that if we would solve the history bug described above, this issue would resolve itself as well. In any case, the dealing with the history of the playground is underdeveloped. So, let’s see if we can identify ways to improve the situation. What do you think? Cheers, Doru > On Aug 31, 2016, at 12:00 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > > At this point I’ve lost cumulatively hours and hours of work due to > Playground not saving the code; so every time I crash I lose. > > In the picture below the code was demonstrably executed and yet it’s not in > the history and if I would crash (which happens several times a day in > “stable” pharo 5) I would lose it. Not to mention that way too often I see > duplicate events in the history with identical code… > > <F091EED2725D4C679C390F5BC76E1CE3.png> > > Peter > <F091EED2725D4C679C390F5BC76E1CE3.png> -- www.tudorgirba.com www.feenk.com "Speaking louder won't make the point worthier."
