Base EditorObject class that every large object in a track extends
The EditorObject needs to contain everything common to an editable object. These objects include, for example, TrackSection, obstructions and scenery.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Essential
- Drafter:
- David Schneider
- Direction:
- Needs approval
- Assignee:
- David Schneider
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- David Schneider
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Stuff common to an editable object:
-Databank. EditorObject can contain the databank that everything is going to need anyway.
-Save and load. EditorObject can handle the common saving and loading, such as
--Marking the datatype
--Saving the databank
--Saving the ID
-Notifying the editor of an update to the object, and receiving a request to update generated data*
--Receiving and update request can be virtual, or there might be a wrapper around a virtual function.
-Receiving a request to fill an octree
-Notifying the editor of a new undoable action, and processing an undo request
--Again, might be a wrapper around a virtual function, or just a virtual function
*"receiving a request to update a generated component"
-some types of objects (such as tracksections) have some of its state dependent on other parts of the state. using this would take the current state and regenerate the dependent parts.
-this is different from filling an octree, which takes the current state and generates displayable elements, adding them to the octree and relinquishing control over them.
Common Databank entries:
-none?
Work Items
Dependency tree
* Blueprints in grey have been implemented.
