On Mon, Mar 14, 2011 at 7:41 AM, Guillermo Polito <guillermopolito@gmail.com> wrote:
I would say that it configures the step, not force.�� The one who forces this message send is WorldState :).


And this one:

I'm a MorphicAlarm to be queued in WorldState list of stepping actions. I hold the stepTime (refresh period) of my receiver / Morph (if nil, the #stepTime value of my receiver is used).

See��
- WordState>>runLocalStepMethodsIn: �� (where the stepping actions are sent).
- WorldState>>startStepping:at:selector:arguments:stepTime: ��(to queue a new StepMessage)

Example:

MorphicUIManager currentWorld
startStepping: (Morph new openInWorld)
at: Time millisecondClockValue
selector: #toggleVisible
arguments: nil
stepTime: 500.


Laurent Laffont -��@lolgzs

Pharo Smalltalk Screencasts:��http://www.pharocasts.com/
Blog:��http://magaloma.blogspot.com/
Developer group:��http://cara74.seasidehosting.st



��


On Mon, Mar 14, 2011 at 3:30 AM, laurent laffont <laurent.laffont@gmail.com> wrote:
This sounds right ?

Laurent

On Sun, Mar 13, 2011 at 8:42 PM, laurent laffont <laurent.laffont@gmail.com> wrote:
Not sure, but try:

I'm a MorphicAlarm to force the step of the receiver at a #stepTime period.

See WordState>>runLocalStepMethodsIn:

Laurent.

On Fri, Mar 11, 2011 at 7:14 PM, laurent laffont <laurent.laffont@gmail.com> wrote:
Today: ��StepMessage


Comment Of The Day Contest - One Day One Comment
Rules:��
#1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s).
#2: If you cannot comment it, deprecate it.
Laurent