I noticed that scheduler controller might calculate width for some columns wrong.
see this picture. All events are absolutely the same, but whereas for other the calculated value is 100px, for dat March 11th is super small 4px, what could be a reason for this? I suppose it might be something with wrong calculation related with February days count, as this view is weekly timeline view and duration 5 weeks. For other months there is no this issue. The scheduler starts from Sunday February 26th. Could you advise what's wrong?
Here is the code for the view:
<ScheduleView Option="View.TimelineWeek" DisplayName="Monthly" IsSelected="@true" Interval="5" MaxEventsPerRow="50" AllowVirtualScrolling="@true">
<ScheduleViewTimeScale SlotCount="1" Interval="1440">
<MajorSlotTemplate/>
<MinorSlotTemplate/>
</ScheduleViewTimeScale>
</ScheduleView>
Hi Valentyn
We prepared a sample based on your shared schedule code snippet at our end. But, we are unable to reproduce the issue. Try our shared sample and If you still facing the issue share the below information to proceed further.
Regards,
Vijay Ravi
Hello,
I reproduced the issue in your sample, please take a look
Thanks
Valentyn
Valentyn,
We confirmed your reported problem “e-appointment width wrong calculation” as a bug and logged the defect report. The fix for this defect will be included in our upcoming weekly patch release, which is expected to be rolled out by 21st March 2023. We will let you know once the fix for the issue is included on March 22, 2023. You can track the status of the fix at the following link:
Feedback : https://www.syncfusion.com/feedback/41844/appointment-width-calculation-is-incorrect
Disclaimer: Inclusion of this solution in the weekly
release
may change due to other factors including but not limited
to QA checks and works reprioritization.
Valentyn,
We are glad to announce that our Essential Studio 2023 Volume 1 release v21.1.35 is rolled out and is available for download under the above link. In this release, the fix for the issue “Appointment width calculation is incorrect” has been included. Upgrade to the latest version to resolve the issue.
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.