Logic behind Object>>featuresAffectedByAction: ?

VA Smalltalk is a "100% VisualAge compatible" IDE that includes the original VisualAge technology and the popular VA Assist and WidgetKit add-ons.

Moderators: Eric Clayberg, wembley, tc, Diane Engles, solveig

Logic behind Object>>featuresAffectedByAction: ?

Postby marten » Tue Jul 08, 2008 10:48 am

I do not understand the logic behind this method.

When one executes an "action" (of a part) the method Object>>abtSignalActionEvents: actionName is called. This method queries, which features are affected by the executed action by asking "featuresAffectedByAction:". Per default it returns #self and this means, that abtSignalFeature: featureName is executed and causes ALL defined events to fire ????

As an example: the method "action" is defined as an action within a part.

(Delay forMilliseconds: millisecondsToWait) wait.
CwAppContext syncExecInUI: [ self signalEvent: #fire: with: millisecondsToWait ].
] forkAt: Processor userSchedulingPriority

Executing this method fires the event #fire two times:

* one at once after the action method has been executed with a parameter nil
* after millisecondsToRun with a parameter value of millisecondsToRun

I know this can not be changed - due to history, but one should add this to the product documentation !
Marten Feldtmann, Principal Smalltalk User, Private
SkypeMe callto://marten.feldtmann
Posts: 641
Joined: Sat Oct 14, 2006 7:10 am
Location: Hamburg - Germany

Return to VA Smalltalk 7.0, 7.5 & 8.0

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest