Hi laurentsd,
Thanks for the response. I see the following sample code (and my question is along these lines)
////////////////////////////////////////////////////////////////////////////
private function refreshUi(context:ChassisActionContext):void {
if (context.reference != null) {
// Send a ModelChangeEvent with the modified object to update the UI
dispatchEvent(
ModelChangeEvent.newSingleObjectChangeEvent(context.reference, context.opType));
} else {
// Use a global refresh event when we don't know the modified object,
// in case a new chassis with the same name already exists.
dispatchEvent(new DataRefreshInvocationEvent(DataRefreshInvocationEvent.EVENT_ID));
}
}
////////////////////////////////////////////////////////////////////////////
The above code runs in response to edit/delete chassis action and works very nicely in the context of "actions". However, if I initiate this using a timer from a class outside of these actions, then calling the following code => "dispatchEvent(new DataRefreshInvocationEvent(DataRefreshInvocationEvent.EVENT_ID));" does not refresh the same chassis table view. For example, from the main plugin entry point, if you create a timer that does a repeated refresh call like above, that does not do anything to the chassis view while you are sitting and watching the table view. Imagine that in the chassis example, a separate java thread keeps changing the chassis info periodically and we want the table view to reflect the new information in the table columns by asking the ObjectStore (by calling getAllChassis()) periodically; this is as opposed to the user coming and clicking the refresh button which under the covers goes through the ChassisAdaptor and makes a call to getAllChassis() - How would we do this?
Thank you.
