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

Weird layout when combining multiple long events and multiple short events #1714

Open
mikeyyyzhao opened this issue Jul 29, 2020 · 4 comments

Comments

@mikeyyyzhao
Copy link

mikeyyyzhao commented Jul 29, 2020

Do you want to request a feature or report a bug?

Bug

What's the current behavior?

For 15 min intervals, when you combine long and short events together, the short events truncate and start a weird ladder. The top pic is from react-big-calendar and the bottom picture is from google calendar.

Screenshot 2020-07-29 11 01 16
Screenshot 2020-07-29 11 01 20

I've tried #1530 's solution of setting dayLayoutAlgorithm but it didn't fix this issue either.

Setup:
step=15 and timeslots = 4 for 15 min intervals

You can also replicate this using the dnd calendar on the official site
Screenshot 2020-07-29 17 08 57

What's the expected behavior?

There's no ladder when displaying shorter events alongside longer events. The successive short events should be aligned in the center fo the long event

@mikeyyyzhao mikeyyyzhao changed the title Weird layout when combining long events and short events Weird layout when combining multiple long events and multiple short events Jul 30, 2020
@JakubSirek
Copy link

I have the same problem. With settings: step=30 and timeSlots=2. The problem does not occur when the two events overlap, but there is a problem with the third. Same problem for day, week and workWeek view.

Correct behavior when two events overlap:
correct

Bug when I add the "Test8" event, which is the third overlap:
bug

@mikeyyyzhao
Copy link
Author

Any suggestions on how to fix this?

@JakubSirek
Copy link

I read some bugs here and tried to use their solution, but nothing helped. It's a bug.

Previously, the same problem manifested itself in the second level, where it is now fixed. The same fix is needed for the third level of events.

@milkman4
Copy link
Contributor

Bump on this! Has anyone come up with a solution or workaround?

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

No branches or pull requests

3 participants