Open pomodoren opened 2 years ago
One possible solution is that we can create a new pointer for rendering only for search.
Practically a ghost_parent
and when saying render_tree
I render based on ghost parent, not parent itself.
I can create a cleanup on each search.
This is a dirty solution, but its better than duplicating the data.
On the other hand, there is always the sqlite idea - keep the data on the side, and reach on need.
No need to re-invent the wheel here.
Because of the problem of pointers of objects, we are using deep copy for now. Still the problem increases in scale if we want to use the results of the search in an analysis sense.
In this case the problem will become more problematic once increase in scale.