Epicea should ask before recovering
Hi, 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) Peter
Me three Recover dialog is standard on all apps anyway On Sun, 16 Apr 2017 at 16:22, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2017-04-16 12:09 GMT+02:00 Peter Uhnak <i.uhnak@gmail.com>:
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)
Me too
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 <kilon.alios@gmail.com> wrote:
Me three
Recover dialog is standard on all apps anyway On Sun, 16 Apr 2017 at 16:22, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2017-04-16 12:09 GMT+02:00 Peter Uhnak <i.uhnak@gmail.com>:
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)
Me too
Hi Martin. 2017-04-18 0:22 GMT+02:00 Martin Dias <tinchodias@gmail.com>:
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.
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 :) On Tue, Apr 18, 2017 at 10:03 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi Martin.
2017-04-18 0:22 GMT+02:00 Martin Dias <tinchodias@gmail.com>:
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.
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
Precisely. (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 :)) Peter
:)
On Tue, Apr 18, 2017 at 10:03 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi Martin.
2017-04-18 0:22 GMT+02:00 Martin Dias <tinchodias@gmail.com>:
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.
Hi, I am interested in this issue. Maybe I will try adding this feature of a pop up when an image crashes, which asks 'do you want to recover your lost changes?' Rajula -- View this message in context: http://forum.world.st/Epicea-should-ask-before-recovering-tp4942281p4942694.... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On Wed, Apr 19, 2017 at 9:42 PM, Rajula Vineet <Vineet.Reddy@iiitb.org> wrote:
Hi,
I am interested in this issue. Maybe I will try adding this feature of a pop up when an image crashes, which asks 'do you want to recover your lost changes?'
Rajula
Give it a go. http://pharo.org/contribute-propose-fix https://pharo.fogbugz.com/f/cases/19955/Epicea-should-ask-before-recovering For approach, use "World menu > Tools > Finder > Source" searching for the window title "Lost Changes Detected". Drop a "self halt" at the top of that method. Save the Image, then change any random method and Quit the image. Next startup a debugger should open in the appropriate spot. ------- However a side question is, when someone goes "World menu > Quit" should that be taken to mean they are throwing away outstanding changes? ------- Something else, I went to test previous behaviour of Lost Changes in Pharo 5.0 and I'm confounded by this behaviour. Preparation... 1. Downloaded and uznipped http://files.pharo.org/platform/Pharo5.0-linux.zip 2. From the command line, ran ./pharo 3. Opened System Browser on random method EllipseMorph>>closestPointTo: 4. Appended "aPoint + 0@0" and saved method. 5. Save&Quit Image, then re-opened Image Test... 6. Changed 0@0 to 1@1. 7. At the command line, hit <CTRL-C> to crash-stop the image 8. Re-open image ==> Expect "Lost Changes" dialog but there is none. Do I misremember the expected behaviour? This is the same with... http://files.pharo.org/platform/Pharo2.0-linux.zip cheers -ben
I as trying to write little tips. But I realized new issue 19957 <https://pharo.fogbugz.com/f/cases/19957/Sometime-Epicea-do-not-see-lost-chan...> 2017-04-20 3:34 GMT+02:00 Ben Coman <btc@openinworld.com>:
On Wed, Apr 19, 2017 at 9:42 PM, Rajula Vineet <Vineet.Reddy@iiitb.org> wrote:
Hi,
I am interested in this issue. Maybe I will try adding this feature of a pop up when an image crashes, which asks 'do you want to recover your lost changes?'
Rajula
Give it a go. http://pharo.org/contribute-propose-fix https://pharo.fogbugz.com/f/cases/19955/Epicea-should-ask- before-recovering
For approach, use "World menu > Tools > Finder > Source" searching for the window title "Lost Changes Detected". Drop a "self halt" at the top of that method. Save the Image, then change any random method and Quit the image. Next startup a debugger should open in the appropriate spot.
-------
However a side question is, when someone goes "World menu > Quit" should that be taken to mean they are throwing away outstanding changes?
-------
Something else, I went to test previous behaviour of Lost Changes in Pharo 5.0 and I'm confounded by this behaviour.
Preparation... 1. Downloaded and uznipped http://files.pharo.org/ platform/Pharo5.0-linux.zip 2. From the command line, ran ./pharo 3. Opened System Browser on random method EllipseMorph>>closestPointTo: 4. Appended "aPoint + 0@0" and saved method. 5. Save&Quit Image, then re-opened Image
Test... 6. Changed 0@0 to 1@1. 7. At the command line, hit <CTRL-C> to crash-stop the image 8. Re-open image ==> Expect "Lost Changes" dialog but there is none. Do I misremember the expected behaviour?
This is the same with... http://files.pharo.org/platform/Pharo2.0-linux.zip
cheers -ben
participants (7)
-
Ben Coman -
Denis Kudriashov -
Dimitris Chloupis -
Guillermo Polito -
Martin Dias -
Peter Uhnak -
Rajula Vineet