Calendar events overlap problem on future week view (showcase 13.0p)

[michalg]

Hi,
There is a problem with overlapping events on calendar week view when current date is shifted into future (next week).
To reproduce in current showcase (tested in 13.0p 2022-04-27):

• run Event Overlapping example (https://www.smartclient.com/smartgwt...endar_category)
• add first event
• add second event selecting the same hours

You can see two events sharing the same cell - so far, so good. Now:

• change week to the next one in future (using right arrow on date chooser widget)
• add first event

One problem here: new event is not shown, but it is there - go week back and next and it is shown now.

• add second event selecting the same hours

The same problem as above - second event not initially shown, but it is there - go week back and next.
Another problem can be seen now: there are two events sharing the same cell, but this time one hides another. Delete one and you can see that there was another under it.

Here is video captured to illustrate:

Thanks,
MichalG

[Isomorphic]

Thanks for the report - this was an issue where internal start and end datetimes on the grid-fields not being updated properly when the range was changed. It's been fixed for tomorrow's builds, dated April 28 or later.

[michalg]

Verified as fixed in 13.0p 28-04-2022.
Many thanks for fast response.
MichalG

[LukeTucker]

We were also experiencing this on 12.1, but found that the latest build (of 12.1) fixes it. However the fix does not seem to work when using UTC time. See sample program below:

package com.mycompany.client;
import java.util.Date;
import com.google.gwt.core.client.EntryPoint;
import com.smartgwt.client.util.DateUtil;
import com.smartgwt.client.widgets.calendar.Calendar;
import com.smartgwt.client.widgets.calendar.CalendarEvent;

public class HelloWorld implements EntryPoint {
    private static int year = 122;
    private static int month = 8;
    private static int start = 29;

    @Override public void onModuleLoad() {
        DateUtil.setDefaultDisplayTimezone("+00:00");
        Calendar calendar = new Calendar();
        calendar.setData(getRecords());
        calendar.draw();
    }

    public static CalendarEvent[] getRecords() {
        return new CalendarEvent[] {
            new CalendarEvent(1, "Meeting1", "Meeting1", new Date(year, month, start + 1, 8, 0, 0), new Date(year, month, start + 1, 18, 0, 0)),
            new CalendarEvent(2, "Meeting2", "Meeting2", new Date(year, month, start + 1, 13, 0, 0), new Date(year, month, start + 1, 15, 30, 0))
        };
    }
}

[LukeTucker]

Results using local time vs UTC time attached.

[Isomorphic]

Thanks for the report - we'll take a look and update here when we have more information.

[Isomorphic]

We've made a change to address this issue for builds of 12.1+ dated September 29 or later

[LukeTucker]

Thanks, we'll give it a try.

[LukeTucker]

We tried again with 12.1 (2022-09-29) and still found problems. The developer reports:

"The problem still persists (see new picture attached). In the example app, I used the following dates:

private static int year = 122;
private static int month = 8;
private static int start = 30;
new CalendarEvent(1, "Meeting1", "Meeting1", new Date(year, month, start, 2, 0, 0), new Date(year, month, start, 23, 59, 59)),
new CalendarEvent(2, "Meeting2", "Meeting2", new Date(year, month, start, 13, 0, 0), new Date(year, month, start, 15, 30, 0))

When you access the page for the first time, the events are aligned correctly. However, if you just edit the longer event (Meeting1) and change the end time to 22:59, for example, the error happens again."

New screenshot attached.

[LukeTucker]

Should I raise a new support request for the issue above?

[Isomorphic]

No, please do not raise a redundant support request. As far as we can see, you have not purchased support, and this issue is unique to you, so it has not received priority. If you need priority assistance with a problem that is only affecting your application, please purchase a support plan. Thanks.