Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

complete option in ChronologyParams #20

Open
josephlarralde opened this issue Aug 20, 2022 · 0 comments
Open

complete option in ChronologyParams #20

josephlarralde opened this issue Aug 20, 2022 · 0 comments
Labels
question Further information is requested

Comments

@josephlarralde
Copy link
Contributor

I just came across these lines while trying to refactor the Chronology class :

// If it IS empty, register the bufferSet as incomplete.
if (params.complete && insertSet.events.empty())
incompleteEvents.push_back({bufferSet,&fifo.back()});

I'm wondering if it is sufficient to check if bufferSet is incomplete : what if insertSet is not empty but not all start events in bufferSet have a matching end in insertSet ? I didn't actually try it though ...

Meanwhile, I'm in the process of refactoring the core in order to make the base Renderer class template lighter, and implementing various types of Renderers on top of it, so I'm starting to think that the "complete" logic could be handled by a specific Renderer implementation, instead of being handled by the Chronology.

I'll keep it in the Chronology for now, but I think it's worth considering the alternative (rewrite in C++ the original naive JS code that only takes start events into account and generates the end events according to the commands).

@josephlarralde josephlarralde added the question Further information is requested label Aug 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant