[Etoys-notify] [JIRA] Updated: (SQ-65) TextMorph avoidOcclusion badly broken

jira at immuexa.com jira at immuexa.com
Tue Apr 28 18:10:57 EDT 2009

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

Scott Wallace updated SQ-65:

    Fix Version: someday
                     (was: triage)

Moving this to "someday" for now since this is not really part of the "etoy experience"; however (this for Karl ;-) when/if you have a fix that you consider complete enough to be worth pushing forward with, please put it out, and maybe we can get this fixed this year.  However, my instinct is that this is a demo feature that probably is not robust enough for use by lay users...

> TextMorph avoidOcclusion badly broken
> -------------------------------------
>          Key: SQ-65
>          URL: http://tracker.immuexa.com/browse/SQ-65
>      Project: squeakland
>         Type: Bug
>   Components: etoys
>     Reporter: team
>     Priority: Eventual
>      Fix For: someday
>  Attachments: TextContainer.kfr.3.cs
> TRAC ticket 4765 (Karl Ramberg, Nov 2007) TextMorph avoidOcclusion is badly broken. It renders the text invisible.
> attachment: TextContainer.kfr.3.cs (335 bytes) - added by karl Nov 2007 - suggested fix to TextContainer 
> (Karl) It seems TextContainer avoidsOcclutions is dependent font. I had to add two methods to TextContainer to make it work at all: TextContainer>>right and TextContainer>>withRight: If I change the font to anything but BitstreamVeraSans, avoidsOcclutions kind of works. With BitstreamVeraSans text becomes invisible.
> (Scott) Worked around in etoys3.0 update 2036occlusionsProb-sw, whose preamble reads:
> In view of the various ways that the the avoid-occlusions feature seems now to be broken (probably for many years), the most prudent thing to do would seem to be to remove the ability to turn this feature on from the UI. So that is what this update does.
> In some future release, someone may wish to revisit this issue: re-enable the menu item, reproduce the issues, fix them... But for now, we cut the Gordian knot..
> (Karl) I think there is a issue with text container not being initialized when a text is pulled out to the world. All efforts to use avoidOcclusion will then fail. When you change font, text container will be initialized and thus the avoidOcclusion work (at least some stuff happen to the text :-) ) The fix I added to this ticket help getting text container to work after being initialized.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

More information about the Etoys-notify mailing list