On 22 December 2012 13:56, Levente Uzonyi <[email protected]> wrote: > On Sat, 22 Dec 2012, Fernando Olivero wrote: > >> Well, the assignment within the and: block says it all… > > > Yeah, blame and flame everyone who doesn't write code the way you do... > But before you do that, tell me what's wrong with that assignment. >
No need to take it so seriously. I do not know what's wrong with assignment, but taking special action depending on specific class of outer morph smells bad. I'm not saying that i know the right solution to deal with such situation, but apparently it should not be like that. > > Levente > > >> >> Fernando >> >> >> On Sat, Dec 22, 2012 at 2:57 AM, Igor Stasenko <[email protected]> wrote: >> StringMorph>>boundsForBalloon >> "Some morphs have bounds that are way too big. This is a >> contorted >> way of making things work okay in PluggableListMorphs, whose list >> elements historically have huge widths" >> >> | ownerOwner | >> ^ ((owner notNil and: [(ownerOwner := owner owner) notNil]) >> and: >> [ownerOwner isKindOf: PluggableListMorph]) >> ifTrue: >> [self boundsInWorld intersect: ownerOwner >> boundsInWorld] >> ifFalse: >> [super boundsForBalloon] >> >> -- >> Best regards, >> Igor Stasenko. >> >> >> > -- Best regards, Igor Stasenko.
