Cool it's not just me and a strange setup :) tx. I'll open an issue then.

On Thu, Dec 6, 2012 at 2:59 PM, Camillo Bruni <camillobruni@gmail.com> wrote:

that is indeed very strange. I can fully reproduce your issues.

that means all delays are corrupted when saving the image? :D
However this has only nasty side-effects for Delays that are currently used
for waiting, otherwise the endTime will simply be refreshed when waiting the
next time.

=> serious bug report!

On 2012-11-29, at 11:55, Guillermo Polito <guillermopolito@gmail.com> wrote:
> Hi,
>
> When using a Delay and saving the image, the delay becomes stupidly broken.
> Look at this:
>
> With the following code
>
> Object subclass: #DelayBug
> instanceVariableNames: 'delay process'
> classVariableNames: ''
> poolDictionaries: 'private'
> category: 'DelayBug'
>
> start
> delay := Delay forMilliseconds: 300.
> process := [ [ Transcript logCr: 'test'. delay wait . false ] whileFalse: [
> ] ] fork.
>
>
> - Then evaluate.
>

> *db := DelayBug new.*
> *db start.*
>
> - inspect
>
> *db instVarAt: 'delay'.*
> *

> *
> The delay seems ok.
>
> - save the image
>
> The delay has a stupid time to be finished :/
>
> Guille