can we modify epicea before asking for recovery?
Because right now when I close image to intentionally throw away changes (because I managed to break the image or whatever), Epicea will freeze the image on startup for 10-15 seconds for even a mere 6-method change.
(I also had it freeze for (couple) minutes on a rather big changeset...)
Closing image and reopening is a very convenient way to get back to usable state of the image, so maybe a configuration option that would first prompt me "Epicea has detected lost changes, do you want to review them? <yes> <no>" would be nice.
Of course if I am the only person that uses images in such a way then I can just work around it myself. (because having endless lists of config options is also nightmare)
You can disable it: World Menu > Settings > Tools > Epicea > Detect lost events on start up
I can make it initially disabled by default.
However, I have an optimization that can improve a lot the time to read, maybe we can still integrate a new version of Epicea before 6.0 release. I've been testing it for a couple of weeks and works well.
On Sun, Apr 16, 2017 at 11:09 AM, Dimitris Chloupis <[hidden email]> wrote:
Recover dialog is standard on all apps anyway
On Sun, 16 Apr 2017 at 16:22, Denis Kudriashov <[hidden email]> wrote:
On Wed, Apr 19, 2017 at 10:04:01AM +0200, Guillermo Polito wrote:
> Yeh, What they mean is that instead of loading the list of "possible stuff
> to recover" you launch at startup a dialog:
> "It seems your last Pharo session exited without saving some code. Do you
> want to recover it?" YES/NO
(and reading my original mail I've realized that I should not write when I am tired... the first sentence there made no sense at all... sorry :))
> On Tue, Apr 18, 2017 at 10:03 AM, Denis Kudriashov <[hidden email]>
> > Hi Martin.
> > 2017-04-18 0:22 GMT+02:00 Martin Dias <[hidden email]>:
> >> You can disable it: World Menu > Settings > Tools > Epicea > Detect lost
> >> events on start up
> > Idea to not disable it but to show notification about lost changes with
> > button to open changes browser. It should remove delay on image startup
> > because full changes will be not loaded in that case.