Status: New
Owner: ----
Labels: Type-Bug
New issue 7207 by
[hidden email]: Solution for issue 3882 introduced
bugs with scaling and moving ImageMorphs using Morphic Halos
http://code.google.com/p/pharo/issues/detail?id=7207Pharo image: core
Pharo core version: Pharo 1.4 #14457
Virtual machine used: linux (from the 1.4 one click.app)
Steps to reproduce #1:
1. Open Halos on an ImageMorph (such as the Pharo ImageMorph on the main
screen)
2. Use the move halo to move the ImageMorph. Once the mouse button is
released, the debugger opens. (I have not included the stack trace in this
report, the explanation below explains what the problem is.)
Steps to reproduce #2:
1. Open Halos on an ImageMorph (such as the Pharo image on the main screen)
2. Use the "Change Scale" halo to scale the ImageMorph larger. Scale
again, back down to the original size. Once the mouse button is released,
the debugger opens.
To fix the issue described here
http://code.google.com/p/pharo/issues/detail?id=3882, code was introduced
which make ImageMorphs respond "true" to the message "isFlexMorph", as
TransformationMorphs do. Although this code does allow the previously
unscalable ImageMorph to scale, it introduces the two bugs listed above,
because ImageMorphs do not respond to all of the messages that
TransformationMorph responds to.
(By looking and the senders of 'isFlexMorph', it is clear to see that
ImageMorph does not implement the required methods, nor should it)
I'm not very familiar with Monticello, and it appears as though I pushed my
changes to
http://ss3.gemstone.com/ss/Pharo14, as
Morphic-WilliamSix.1144.mcz. I thought I was saving my changes locally,
and did not expect that my action could nor would push changes elsewhere.
I need to read more to understand Monticello workflow.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
