Task - #169 - Refactor SimulationObjectInstance - Keep Reference to SimulationFunctions

Project: Antilia (alpha) Priority:
X
 Blocking
Type:
Refactor
Status:
New
Reported By:
jeff 
Assigned To:
jeff 
Created On: September 25, 2020 Resolved On: -

Is This Bug Affecting You?


Users Reporting This Issue: 1

I am Affected!
 
Add a Comment

Currently SimulationObjectInstance has several functions into which a ServerSimulationFunctions or ClientSimulationFunctions class must be provided. This class will never change after activation, so it makes sense to have the instance simply store a reference to this class and clean up all the function calls that reference it.

The instance should also provide access to these classes as it is really the component classes that make use of these features.

Consider this change carefully - are we really cleaning things up or are we sewing confusion? Is there a better way to provide access to these functions without needing to pass a reference around?


Highlights
Comments Only
All Activity

Friday, September 25, 2020

jeff 
 
Priority changed from
4
 Low to
X
 Blocking
Reason:This is blocking progress on rebasing SimulationObjectInstance onto SceneObject.
jeff 
 

New Task Created!

Currently SimulationObjectInstance has several functions into which a ServerSimulationFunctions or ClientSimulationFunctions class must be provided. This class will never change after activation, so it makes sense to have the instance simply store a reference to this class and clean up all the function calls that reference it. The instance should also provide access to these classes as it is really the component classes that make use of these features. Consider this change carefully - are we really cleaning things up or are we sewing confusion? Is there a better way to provide access to these functions without needing to pass a reference around?
Page:
Page: 1