[Etoys-notify] [JIRA] Updated: (SQ-232) Simple test project demonstates problem with objects embedded into rendered morphs

[jira at immuexa.com]

     [ http://tracker.immuexa.com/browse/SQ-232?page=all ]

Scott Wallace updated SQ-232:
-----------------------------

    Attachment: forwardFix-sw.1.cs.gz

Thanks, Jerome.  This project exposes an obscure bug, (YATMB - Yet Another TransformationMorph Bug) which the attached fileout purports to fix -- please test!  

Note that the "fence" which is used in conjunction with "forward" is a feature only of paste-up-morphs (playfield or World), not of just any morph (e.g. not the Rectangles in your example.)   So objects that are scripted to move "forward" are normally expected to reside directly in some playfield (or directly on the desktop/world), if one expects the "fence" and "bounce" to work reasonably.  Sending "forward" to an object which is embedded in a non-pasteup, which itself is tilted, is a pretty extreme case, in which it's not even clear what the user's reasonable expectation should be.  But the attached fileout, at least, fixes the clear-cut bug exposed by the example.



> Simple test project demonstates problem with objects embedded into rendered morphs
> ----------------------------------------------------------------------------------
>
>          Key: SQ-232
>          URL: http://tracker.immuexa.com/browse/SQ-232
>      Project: squeakland
>         Type: Bug
>   Components: etoys
>     Reporter: Jerome Peace
>     Priority: Ongoing
>      Fix For: review
>  Attachments: dizzy and confused.003.pr, dizzy.pr, forwardFix-sw.1.cs.gz
>
>
> The transformation morph used for rendering fights the basic concept of morphs being built up by agglomerating other morphs.
> In particular when you embed a morph then tilt its owner. The direction of the embedded morph gets a little confused as does its idea of where the boundaries of its owner lie.
> I don't have a good solution for this bug. A while back I did come up with a very simple illustration of it which I put in project form.
> This bug report is an excuse to upload the project.
> It helps document the current state of a rather intractable problem.
> What should happen is the moving pieces should continue their journey's w/o bouncing til at real edge of their tilted container.
> Their is no estimate of the time. Trying the test is very simple. 5m
> Fixing things so the tests work right. Is indefinite at this point.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://tracker.immuexa.com/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira