Recent update render the result to dissfunctional ?

Hi Yordan,

We have validated the reported issue and let you know that it works fine as expected. Kindly try the attached sample and the video.

Could you please share the scheduler rendering code snippets and the package version to proceed to validate further and provide the prompt solution earlier?

Regards,

Ruksar Moosa Sait

Well. It was great wasting of time again, but AGAIN - it is 

EnableAutoRowHeight="true" which is totally crashing the component.

Anyway if I turn it to "false" then the old bug appears - not showing all of the events.

It's like an endless carousel - fixing a bug opens an old one which opens a new one, which fixing open an old one.. :|

Can you please confirm the issue by watching the below video demo?

https://www.syncfusion.com/downloads/support/directtrac/general/ze/ISSUER~1-236951003.zip

Hello. Yes. This is bug #2, #3 and #4 in the new version.

The bug #1 is that the events is not inside the cells, but somewhere between the cells..

Hi Yordan,

Thanks for the update.

We have considered the reported problem as a defect at our end and logged the defect feedback. The fix for this issue will be included in our 2022 Volume 1 release which is expected to be rolled out by the end of March.

https://www.syncfusion.com/feedback/33559/appointments-are-misaligned-when-performs-expand-collapse-resources

Regards,

Vengatesh 

Hi Yordan,

We are glad to announce that our Essential Studio 2022 Volume 1 release v20.1.0.47 is rolled out and is available for download under the following link.

https://www.syncfusion.com/forums/174125/essential-studio-2022-volume-1-main-release-v20-1-0-47-is-available-for-download

In this release, an issue with “Appointments are misaligned when performs expand/collapse resources” has been fixed. As a result, we recommend you upgrade to the latest version of our Syncfusion package to avail of those changes.

Release notes: https://blazor.syncfusion.com/documentation/release-notes/20.1.47?type=all#scheduler

From our Volume 1 2022 release(v20.1.47), we have introduced some breaking changes. Please find the below changes from the release notes.

Release notes: https://blazor.syncfusion.com/documentation/release-notes/20.1.47?type=all#breaking-changes

We thank you for your support and appreciate your patience in waiting for this release. Please contact us if you would require any further assistance.

Regards,          

Vengatesh

It is not fixed for sure. The problem is still the same, practically nothing have changed in the new version.
The bug is there at the moment i set 

EnableAutoRowHeight to true.

Hi Yordan,

We have checked the reported issue in the new version but unfortunately, we are not able to replicate the issue since the appointments are positioned properly. Could you please check the attached sample and let us know what we have missed replicating this issue? 

it will be very helpful to replicate the issue and provide a prompt solution earlier. 

Regards,

Vengatesh 

Hello.

as in the previous posts the idea is to manage the size of the events, since these events is ginormous. 
So.. adding a style on top of  EnableAutoRowHeight="true" reveal the problem.

add this source to the end of your demo, and the issue will appear right away

<style>

    .e-schedule .e-timeline-view .e-resource-cells,

    .e-schedule .e-timeline-month-view .e-resource-cells,

    .e-schedule .e-timeline-view .e-appointment, .e-schedule .e-timeline-month-view .e-appointment

    {

        height: 29px !important;

    }

    .e-schedule .e-timeline-view .e-work-cells,

    .e-schedule .e-timeline-month-view .e-work-cells

    {

        height: 31px !important;

    }

</style>

AllowVirtualScrolling must be "false" as well, since it's not applicable.

Hi Yordan,

Thanks for the update.

We have checked the reported issue with the shared code snippet and we found the cause of the issue is that you have set the !important for the work-cells and provided different height values for work-cells and resource cells which cause the problem for the reported issue. 

So we recommend using provide the same height for the work-cells and resource-cells and remove !important for the height property of it. Because the height value will be assigned dynamically at the source end when we enable the EnableAutoRowHeight . Please find the below code snippet.

Please find the below-attached sample and let us know if you need any further assistance.

Regards,

Vengatesh

Attachment: Blazor_sample_cc5762a8.zip

The whole point is height NOT to be assumed dynamically. I need it perfectly in specific size, since I have to have a million inch monitor for like 2000+ events / day.
The whole thing were working properly about 10 versions before the current. Then the bugs in the new versions start to pile up, ending with a project with spend a lot of time which initially working, but then scratched out from the updates.
On top of it - it is literally looking absurdism with an event as big as 1/10 of the screen on a small monitors.
This is antiproductive at the best. On top of it - it is literally an unwanted result view.
Aside of this all of the meant above was advice by your support to be made this way.
Therefore I was just advices to scratch out about 9 months work and advices, and waiting and waiting, because some bug you have is not repairable ?!
This is quite annoying.

There, You've just told me to scratch out these "helps" :
https://www.syncfusion.com/forums/172214/events-is-not-overlaping-but-yet-not-shown
https://www.syncfusion.com/forums/172262/keep-everything-inside-the-window-without-horizontal-scrolling
https://www.syncfusion.com/forums/172161/remove-empty-space-on-height

This is really unreliable behaviour, or top of a promises that it will be fixed, not I am getting "just scratch out everything you did, and it was told You or promised to You".. 

Hi Yordan,

Sorry for the inconvenience.

We have created a new ticket under your account to follow up with this query. We suggest you follow up with the ticket for further updates. Please log in using the below link.

https://support.syncfusion.com/support

Regards,

Vengatesh

Hi Aramis,

We have checked the events rendering with EnableAutoRowHeight property and it's been working as expected. So could you please share more details of your problem? It helps us to proceed to validate further and provide the solution earlier.

Regards,

Vengatesh 

It doesn't !
Please read the discussion. The bug is more than a year old and start to stucking a bug on top of another bug.
Please read the discussion above.

Hi Yordan & Aramis,

We have created a ticket under your respective Syncfusion account. So, we request you to follow that for further technical assistance. Please log in using the below link.

https://support.syncfusion.com/support

Regards,

Vengatesh 

Here a proof that it doesnt work as expected : 

Hi Yordan,

Thanks for the update.

We have checked the sample and we provided the solution for this problem in our previous update. But we have deeply analyzed your problem in this sample with your previous quires which are listed in your previous updateand we suspect that you need to set the events height as full height of the row without +1more indicator.

If so, we suggest using the IgnoreWhiteSpace property to occupy the events as full height of the row, and as well need customize the respective CSS class like below.

You can find the same in the below-attached sample. Please check the sample and kindly let us know if this meets your requirement.

Regards,

Vengatesh

Thanks for the update.

mobdro

vidmate

Thank You very much dear  Vengatesh Maniraj and support fellows !
Sorry if I gave You hard time !

Hi Yordan,

You are most welcome!!!

We are happy to assist you.

Please get in touch with us if you need any further assistance.

Regards,

Vengatesh 

Thank You very much dear

You are most welcome!!!

Hello. Yes. This is bug #2, #3 and #4 in the new version.

Hi Flax,

We have conducted tests on our end using the latest version and found that it is functioning as expected.

For your convenience we have prepared a sample, kindly check on the attached sample, Also your reference, we are attaching a GIF of our testing process.

If you continue to encounter these issues, it would greatly assist us in identifying the problem if you could provide additional details about your setup or a simple sample that replicates the issue.

Regards,

Ram