[Cuis-dev] LayoutMorph subclass instance #beColumn has not effect

[Alexandre Rousseau]

I looked at the commit ...

 aMorph == self ifTrue: [^ self error: 'cannot be own submorph'].


but this will not save me from a more insidious mistake such as ...

m1 = Morph new.
> m2 = Morph new.
> m3 = Morph new.

m1 addSubmorph: m2.
> m2 addSubmorph: m3.
> m3 addSubmorph: m1.


Anyway, I didn't want to complicate your life/lives.   Thanks for this. It
will help reduce some mistakes.

A.


On Mon, Mar 13, 2023 at 4:12 PM Juan Vuletich <juan at cuis.st> wrote:

> On 3/13/2023 1:36 PM, Alexandre Rousseau via Cuis-dev wrote:
>
> Defining a class as subclass of LayoutMorph and initializing it thus:
>
> initialize
>>   super initialize.
>>   self beColumn.
>
>
> morphs added to it still appear next to each other, horizontally, as if
> #beColumn was ignored.
>
> Is this expected behaviour for a subclass of LayoutMorph?
>
>
> You may want to play with LayoutMorph class >> example1, that shows a
> possible way to build a column of rows. There are several other examples
> there. #example101VG is particulary interesting.
>
> After opening them, play with the halo handles, to see how they react.
>
> HTH,
>
> --
> Juan Vuletichcuis.stgithub.com/jvuletichresearchgate.net/profile/Juan-Vuletichindependent.academia.edu/JuanVuletichpatents.justia.com/inventor/juan-manuel-vuletichlinkedin.com/in/juan-vuletich-75611b3twitter.com/JuanVuletich
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20230313/1892bfc7/attachment.htm>