I still don't know why there is no explicit "save", to at least capture that state in the play-stash.
There is an explicit "publish" to the cloud, but no save.��

Esteban A. Maringolo


On Wed, Jun 19, 2019 at 2:34 PM Sven Van Caekenberghe <sven@stfx.eu> wrote:
if you give the playground's tab a name, it will save it under that name in pharo-local/play-stash - which I found reasonably reliable.

> On 19 Jun 2019, at 15:38, Peter Uhnak <i.uhnak@gmail.com> wrote:
>
> Hi Hilaire,
>
> this is a known problem. I've been losing code to Playground for years. (e.g. using undo (ctrl+z) is a good way to lose code)
>
> What helps a lot is to look into pharo-local/play-cache directory (you can open Spotter and type in "pharo-local" (without quotes)) which contains a log of probably 90% of playgrounds you executed.
>
> There are still some conditions under which you can lose code even with play-cache (e.g. ctrl+z sometimes)... so good to keep that in mind.
>
> Peter
>
> On Wed, Jun 19, 2019 at 3:20 PM Hilaire <hilaire@drgeo.eu> wrote:
> Beside that, auto-save is a nice feature, but it needs to be predictable.
>
> Hilaire
>
> Le 18/06/2019 �� 21:53, Hilaire a ��crit :
> > Hi,
> >
> > I have to admit it is working randomly in P7 with Dr.Geo. (19.06 rel)
> >
> > Sometime script can be retrieved with the playpage button other time no:
> > executed script can not be retrieved.
> >
> > Its behavior is not predictable and it is a problem for me and the kids
> > playing code.
> >
> > Hilaire
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>