Yes, this happened due to Monticello when integrating the Issue. Is fixed in the latest image.
Messing up with Color's is both hazardous and difficult to integrate in the remote server! I'm having some problems with the integration of the issue whichs removes TranslucentColor.that I'm tackling now. Fernando On Thu, Sep 12, 2013 at 12:40 PM, Marcus Denker <[email protected]> wrote: > > On Sep 12, 2013, at 12:36 PM, "Torsten Bergmann" <[email protected]> wrote: > >> kilon wrote: >>> this happens only when I try to create a new workspace issuing the commands >>> you see in the screenshot and it appears after I try to move the new >>> workspace. At first it appears as a small red box but while hitting enter it >>> expands to the final size you see here. >>> >>> Are you aware of this bug ? >> >> I can reproduce the problem. Looks like some code is missing and leads to an >> uninitialized >> class variable: >> >> The method #translucentMaskFor:depth: uses a class var "TranslucentPatterns" >> from FormCanvas. >> This class variable is nil and therefore it crashes. Looks like there is >> some initialization >> on the class side missing. >> >> Code is written by Fernando this week (9/11/2013) - so it is brand new. >> >> Looks like a side effect of fixing https://pharo.fogbugz.com/f/cases/11559 >> which was integrated in update #30389 >> >> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-September/083764.html >> >> If you look at the second changeset in this issue #11559 it includes an >> #initializeTranslucentPatterns >> method from Fernando - but it did not made it correctly into the image. >> >> Please open a new bug on http://bugs.pharo.org and maybe Fernando can have a >> look. >> > > This should be fixed in 3.0 390…. at least I can't reproduce it anymore. > > Marcus >
