ExecutableObjectIF: initializeAfterTaskCreation function #138

Closed
opened 2020-07-09 20:13:47 +02:00 by muellerr · 0 comments
Owner

when initialize is called, the task has not been created yet, so setTaskIF was not called yet and can not be used in initialize(). An initializeAfterTaskCreation() function has been added in ExecutableObjectIF.
It is called in the respective task creation functions after the Task IF has been set.
It can be used to cache values like task frequency, if the task needs it.

when initialize is called, the task has not been created yet, so setTaskIF was not called yet and can not be used in `initialize()`. An `initializeAfterTaskCreation()` function has been added in ExecutableObjectIF. It is called in the respective task creation functions after the Task IF has been set. It can be used to cache values like task frequency, if the task needs it.
muellerr added the
feature
label 2020-07-09 20:13:54 +02:00
muellerr changed title from initializeAfterTaskCreation function to ExecutableObjectIF: initializeAfterTaskCreation function 2020-07-09 20:15:44 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#138
No description provided.