Forcing Morphic Updates?
Ned Konz
ned at bike-nomad.com
Sun Jun 15 17:52:22 UTC 2003
On Saturday 14 June 2003 10:39 pm, Aaron J Reichow wrote:
> I just end up with the morph at the upper right hand of the screen,
> with no animation. This problem has also come up with updating a
> PluggableTextMorph while there is processing going on.
>
> This is probably something which has been discussed here a number
> of times, and is probably pretty simple. The only thing I've seen
> so far is the #step system, which works well for this, but there
> has to be another way- subclassing every morph you want to animate
> a little seems to be a bit much. I've tried calling step to try to
> force an update, but same behavior.
You don't have to subclass.
You can step a selector other than #step, so you can use an extension.
So you can say:
someMorph
startStepping: #myMethod: at: startTime arguments: { arg } stepTime:
100
or whatever.
> I guess I could use mixins if there is a package which provides
> that, or implement a new method on Morph- #supplamentalStep: aBlock
> which sends #value to block at the end of beginning of each step
> method. But both seem suboptimal.
So you don't need this.
The advantage of doing this is that your display updates will be
handled as long as you send #changed sometime.
--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE
More information about the Squeak-dev
mailing list
|