Hello Vince,

I could not replicate the issue by your following detail. So, would you mind to send me a simple runable sample that replicates this issue?
FYI, I attached the unrelease hotfix for you. This hotfix has not been fully tested (disclaimer on). Please let me know if the issue still persists after applied the hotfix.

I am sorry. Please ignore the previous message. I am able to replicate it now. But If you use return value is true in GetElement(), it will avoid the error. Currently, the return value should be "true" when retrieving cell element. Would you mind to let us know about your requirement?

Regards,
Handy

Thank you very much for the explanation about the steps to reproduce the issue.

I have reported this issue along with work item #727. I’ll keep you updated with any news I heard from the team about work item #727.

I’d like to inform you that WebScheduler development team has managed to fix the issue. I also have ensure that the issue no longer persist using the nightly-build hotfix of WebScheduler 3. I’ve uploaded the nightly-build hotfix to be tested on your end. Please let us know whether the nightly-build hotfix helps or not.

Please download the nightly-build hotfix of WebScheduler at here.

Note

*The nightly-build hotfix has not been extensively tested (disclaimer on). So, we are really appreciate if you have encountered an issue can kindly give us a feedback of it.

*Please carefully follow the step-by-step shown in this link, in order to apply the hotfix manually.

*Please close all opened Microsoft Visual Studio opened project during applying the hotfix.

*After finish apply the hotfix to your development machine, please don’t forget to apply this hotfix to your own project.

*It is recommended to do ‘iisreset’; clear ‘Temporary ASP.NET Files’ in “C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files” folder; and clear browser’s cache before re-test the issue using the hotfix.

I tested the nightly build hotfix, it solve the issue described here and some other issues reported in other posts created by me. Anyway I think that it introduces some bug in the alignment of the events in the scheduler cells and also in the drag and drop of events, for example I want to show you the screen shot in attachment: as you can see the event selected is in 26th of May but the web callout show that the event should be in 25th of May and querying the database I can see that the event starts on 25th of May as show in the call out.

I will not go more in detail about that because the hot fix is not a released version.

Are there any new about a release date for version 3_0_1000_5?

Regards,

Vince

Thank you for your valuable feedback regarding issues that found on the nightly build of hotfix.

The event alignment in the scheduler cells issue is quite odd and we have not received such reports so far. I tried to reproduce the problem in my local test by using the same build version of WebScheduler nightly build hotfix and the ‘FirstExperience.aspx’ reference sample file in WebSchedulerSamples project, but my efforts were not successful – everything works smoothly and so does the event alignment in the scheduler cells.

I’m afraid that I might miss something during my attempt replicates the issue, so we would need you to elaborate on your specific scenario and possibly give us a step-by-step guide that we can use to observe the problematic behavior.

From the information that I heard, the hotfix is planned to be released at this month. I’ll keep you informed with the release date of the hotfix.

Hi Yudi,

with WebScheduler version 3.0.1000.5 the issue is solved and the bug in the alignment of the events in the scheduler cells and in the drag and drop of events I told you in my last message in this post does not appear.

Regards,

Vince

Glad to hear the good news.

Should you need further assistance or run into any problems regarding our controls, feel free to post it into our forum. We would be happy to assist you again.