When using Vertical Grouping by multiple resources and Timeline View, the group rows without appointments do not have min-height as the rest of the group rows. Thus, they appear shorter which causes an offset of the events on the next rows.

Steps to reproduce:

1. Load Timeline View Demo
2. Delete Charlie's event in Small meeting room

===

ADMIN EDIT

===

A possible workaround for the time being is to set min-height to all rows. Apply this style only when Timeline view is selected, so this does not break the rendering of the other views.

Example: https://blazorrepl.telerik.com/mHYmwsOt30fjTZ6a32.

I am using a Scheduler with vertical grouping by multiple resources. In Timeline view, some of the appointments appear with an offset and are not correctly aligned in the cell. In some cases, the appointment is even rendered outside the slot it is associated with.

The issue seems to occur as of UI for Blazor 4.2.0. The same configuration worked fine in 4.1.0.

• working version (4.1.0)...
  https://blazorrepl.telerik.com/cdOXvcwQ0378eNBL22
  
• not working version (4.2.0)...
  https://blazorrepl.telerik.com/GxEZvwwG04r4TlwA44

I am using the Scheduler component in Telerik for Blazor and am getting an intermittent exception being thrown, usually when navigating quickly through the application (ie. navigating to another page before the initial page containing the Scheduler has finished rendering).

This is the exception received:

===

ADMIN EDIT

===

The Scheduler must render in the browser and then it measures and adjusts its layout with JavaScript. You may hit this error if the component is disposed before or during this JavaScript call.

Example use cases:

• Navigating to a different page before the full component initialization
  
  Workaround: 
  
  The possibility to hit that is higher in case the Scheduler needs more time to initialize (e.g. it has to render a large set of appointments). In such a scenario, it will be useful to optimize the time needed for loading the appointments, so that the initial component rendering is not blocked by waiting all the data. For that purpose, you may load the appointments on demand - not fetching all possible appointments at once, but only when the user should see them. An example of such an implementation you may find here: https://github.com/telerik/blazor-ui/tree/master/scheduler/load-appointments-on-demand.
  
  
• Disposing the component during runtime (e.g. depending on the screen size) - https://blazorrepl.telerik.com/wIuHliEt40SutaBI53.
  
  Workaround: 
  
  Potential solution in this case - render component after calculating the screen size: https://blazorrepl.telerik.com/coEnPWON4570Wna007.

Check the following configuration: https://blazorrepl.telerik.com/cHvuPOYX27peykXr18 ( SlotDuration="720"  SlotDivisions="1").

The start time of the appointment is 12:00 PM today. The Scheduler, however, displays the start at 12:00 AM on the next day even though the arrow indicates the event continues from the previous day.

For reference, if I set SlotDivisions="2", I get the expected result: https://blazorrepl.telerik.com/GxFOvYED302CzPCo32.

The appointments at the start of the day seem accurate. If you scroll down, the position of the appointments does not line up with the grid line for the hour that it starts at or ends at. The issue can be observed in the live demo.

I am trying to look at the times 7pm - midnight.  But if I set the end time to midnight, I get an error that the end time has to be greater than the start time.  How do I set the timeline to show 7pm - midnight or 8pm - 2am?

I tried including the next date in the EndTime but the Scheduler does not take the date into consideration, it checks only the time portion.

If the Start and End match exactly, the rendering of the Scheduler breaks in Day view. If another view is used, the event looks as if it is rendered on the previous day.

===

ADMIN EDIT

===

A possible workaround for the time being is to use a custom edit form and implement some kind of validation that prevents the user from selecting the same value for the Start and End of an event.

I have a problem with Scheduler TimelineView. When there are a bit more appointments in the first resource group, the last appointment from the last group is positioned incorrectly/outside of the Scheduler component.

I think the CSS parameter "top" is calculated in the wrong mode. See the attached recording.

If the Start and/or End fields are DateTime? double-clicking on an empty slot does not open the form. This makes it impossible to create new events.

The issue occurs as of UI for Blazor 3.7.0.

Reproduction: https://blazorrepl.telerik.com/mnEHQNvl48HDc8xb30.

When you have an event that starts between 11:30pm and 12:00am - the default last slot of the Timeline view, the Scheduler throws the following error:

Error: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection

Scheduler cells are not aligned correctly in the Timeline View when Bootstrap Theme is used.

To reproduce the problem:

 1. Open the following Scheduler Demo:
 https://demos.telerik.com/blazor-ui/scheduler/overview

 2. Select the Bootstrap Theme

 3. Open the Timeline View

I have created an event series with the following RecurrenceRule:

RecurrenceRule = "FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR"

However, it looks like the collection of days is not taken into consideration and the events are created for every day of the week as if I have only set:

RecurrenceRule = "FREQ=DAILY"

---

ADMIN EDIT

---

A possible workaround for the time being is to use  "FREQ=WEEKLY" and extend the occurrence to the desired days of the week. For example, targeting the "Morning run" appointment: https://blazorrepl.telerik.com/cQuiFGOK01nSotIT28.

Hi,

I have a recurrent event with the following dates:

"Start": "2022-08-01T07:00:00",
"End": "2022-08-01T08:00:00",
"RecurrenceRule": "FREQ=DAILY;UNTIL=2022-08-04T05:00:00"

https://datatracker.ietf.org/doc/html/rfc5545#section-3.3.10 says:

The UNTIL rule part defines a DATE or DATE-TIME value that bounds the recurrence rule in an inclusive manner.  If the value  specified by UNTIL is synchronized with the specified recurrence, this DATE or DATE-TIME becomes the last instance of the recurrence.  The value of the UNTIL rule part MUST have the same value type as the "DTSTART" property

I generated the events with Thunderbird, synchronized to the caldav-Server and read it from there. 

In the Telerik Scheduler I got only 3 occurences of the event: from the 1st to the 3rd.

In Thunderbird I got 4. From the 1st to the 4th. According with the RFC, Thunderbird is right :-) 

----------------------- ADMIN EDIT -----------------------

The recurrence generation currently considers the time in the recurring rules. To workaround the issue, you should manually change the until parameter to contain the maximum possible hour, minute and second for the day. Here is an example:

// item is your appointment item
var rule = RecurrenceRule.Parse(item.RecurrenceRule);
if(rule.Until.HasValue)
{
    var untilDate = rule.Until.Value;
    rule.Until = new DateTime(untilDate.Year, untilDate.Month, untilDate.Day, 23, 59, 59);
}

item.RecurrenceRule = rule.ToString();

--------------------------------------------------------------------

The following date in the Scheduler RecurrenceRule cannot be parsed and is ignored:

RecurrenceRule = "FREQ=DAILY;UNTIL=20210722T000000"

According to the RFC5545 specification, this should be a valid date format.

These formats will work:

RecurrenceRule = "FREQ=DAILY;UNTIL=2021-07-22T00:00:00"

RecurrenceRule = "FREQ=DAILY;UNTIL=2021-07-22T00:00:00.000Z"

EDIT:

private string TransformRecurrenceRule()
        {
            const string untilSeparator = "UNTIL=";
            var ruleParts = RecurrenceRule.Split(untilSeparator, StringSplitOptions.RemoveEmptyEntries);
            if (ruleParts.Length <= 1)
            {
                // There was no Until clause to worry about
                return RecurrenceRule;
            }

            // Save the first part of the rule
            var ruleBeginning = ruleParts[0];

            // Split the date part of the until clause from any following clauses
            var remainingClauses = ruleParts[1].Split(';', 2, StringSplitOptions.RemoveEmptyEntries);

            //Save the date part of the until clause
            var untilDate = remainingClauses[0];

            // Save any following clauses with the `;` replaced
            var ruleEnding = "";
            if (remainingClauses.Length == 2)
            {
                ruleEnding = $";{remainingClauses[1]}";

            }

            // Convert the until date into .net parsable format
            const string format = "yyyyMMddTHHmmss";
            var date = DateTime.ParseExact(untilDate, format, CultureInfo.InvariantCulture);
            var dateStr = date.ToString("yyyy-MM-ddTHH:mm:ss");

            // recombine rule components
            var newRuleParts = new[] {ruleBeginning, untilSeparator, dateStr, ruleEnding};
            var newRule = string.Join("",newRuleParts);

            return newRule;
        }

That's pretty weird but nevertheless very specific: if the Scheduler is loaded with POCO objects from EntityFramework with LazyLoading enabled (Castle.Proxies objects) them the k-event-drag-hint box is not shown (!)