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

Fix rbc lay algorithm #16

Merged
merged 8 commits into from
Apr 24, 2024
Merged

Conversation

mikeyyyzhao
Copy link
Owner

No description provided.

@@ -32,8 +77,8 @@ class Event {
(max, row) => Math.max(max, row.leaves.length + 1), // add itself
0
) + 1 // add the container

return 100 / columns
// this section handles the logic for container with leaves (in this case all the short events belong to Long_1)
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete

}

// For dev
getEventTitle() {
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete

@@ -183,6 +253,8 @@ export default function getStyledEvents({
event.leaves = []
container.rows.push(event)
}
// Problem: it all belongs to the same row but events that are not actually overlapping are being placed in the same row
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete

@mikeyyyzhao mikeyyyzhao changed the title WIP: fix rbc lay algorithm Fix rbc lay algorithm Apr 24, 2024
@mikeyyyzhao mikeyyyzhao merged commit d30f343 into master Apr 24, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant