ned would it make sense to have that in the image?

Stef

On 24 mars 04, at 18:16, Ned Konz wrote:

On Wednesday 24 March 2004 4:35 am, Ed Cavazos wrote:

...

Hello!

I've only been Squeaking for 2 days so I've got a very elementary question about Morphic layout stuff...

Below is a code snipet which illustrates the problem.

"**************************************************" am := AlignmentMorph new. am extent: 500@500.

picopaint := PicoPaintMorph new. picopaint hResizing: #spaceFill. picopaint vResizing: #spaceFill.

am addMorphBack: picopaint. am openInWorld. "**************************************************"

The PicoPaintMorph is from the "Introduction to Morphic" article by John Maloney.

So after invoking doit, the AlignmentMorph appears and the PicoPaintMorph is inside it. However, the size of the PicoPaintMorph is still it's initial size. That is, it hasn't filled up the remaining space in the AlignmentMorph. If I activate the halo's on the AlignmentMorph and manually resize it, the PicoPaintMorph finally get's resized. How do I get it to fill the space from the very beginning so that it looks correct as soon as I send 'openInWorld' to the AlignmentMorph?

As you've probably guessed, the initial layout doesn't send #extent: so your morph doesn't get resized. Instead it gets sent #bounds:.

Rather than overriding #bounds: as well, a better way to do this might be to check the form size at drawing time.

The attached version of PicoPaint does this by adding an accessor for form that checks to see if the size has been changed and copies the form if necessary.

The two direct references to the form instance variable were replaced with calls to this accessor.

-- Ned Konz http://bike-nomad.com/squeak/ <PicoPaintLazyForm-nk.1.cs>

picoPaint as a good example of bounds/extent: using. I was thikning that picopaint was in the image but this is TinyPain. Another lovely morph.

Stef

On 24 mars 04, at 22:28, Ned Konz wrote:

On Wednesday 24 March 2004 11:19 am, stéphane ducasse wrote:

...

ned would it make sense to have that in the image?

Which "that"?

-- Ned Konz http://bike-nomad.com/squeak/

On Thursday 25 March 2004 12:54 pm, Lex Spoon wrote:

Morph>>bounds: calls #extent:, however.  It sounds like something else is going on.

There are paths through the layout code that don't call #extent:, though, and instead just assign to bounds directly.

Your code deals with the *form* size, not the morph size.  I was about to whine about changing the size of a morph within a drawOn: method, which sounds quite unstable.  How is Morphic supposed to cope, if a morph is asked to draw itself but it changes its size along the way? But the code you post is changing the *form* size, not the size of the morph.  And it is using "self extent" to find the size of the form, thus suggesting that the morph is indeed getting set to the correct size.

Right.

So perhaps the morph was getting resized all along, but it just wasn't drawing in its full area?

The morph was getting resized. However, #extent: was not getting called from the layout method, so the form wasn't getting resized.