Well, that's what you get from having people using some other kind of workflow that the usual one you gurus use since years; they do click on some unforseen button combinations. But frozen it was for sure.
Anyway, cannot send you any image for testing... it was frozen. This makes me wonder: isn't there any way to put a kind of non maskable kind of interrupt key in the VM that would interrupt its execution for sure? I do encounter a tad too many freezes. Some of them my fault but quite some others not really. I now understand why one would have a process saving images with an incrementing number endlessly in the background to avoid just that now. I don't even want to think about life before Monticello ... Yikes! Phil 2013/2/19 Camillo Bruni <[email protected]>: > this is rather strange. > We're using gemstone for all pharo development and we haven't had any > problems with it. > > I loaded all the stuff from your test-repository and it worked. > more details? ;) > > On 2013-02-19, at 22:06, "[email protected]" <[email protected]> wrote: > >> So, I wanted to merge my stuff from the SS3 project. >> >> When loading it needed to have BitBltPen (which I had somewhere as in >> BitBltPen-MarianoMartinezPeck.4.mcz) >> >> I wanted to put that into my SS3 area and so, added the repository to >> the list of repos in monticello, then took the mcz and then added the >> repository to the package. >> >> Net result: Frozen image. >> >> No amount of Cmd-. could do anything. >> >> See screenshot. >> >> ... now restarting VM... >> >> Phil >> <Capture d’écran 2013-02-19 à 22.01.46.png> > >
