User Profile & Activity

Bernard Xiang Member
Page
of 4
Posted: May 23, 2014 4:45 AM
Hi Raj,

I will ask our developer team regarding this issue hotfix. Perhaps, they can give you earlier hotfix to resolve this issue. We are really sorry for this inconvenience and delay for this hotfix release. Hope this helps.

Regards,
Bernard

Hi Frank,

Thank you for your compliment. Please let me know if you have any question regarding for our control. I will gladly help you to resolve it.

Regards,
Bernard

Hi Frank,

I think this problem happen because the function that bound in Calendar cell click event clash with scheduler.Refresh function that you called in client side. This might be happen because WebScheduler do FlyPostback request that shouldn't be interrupted with the other FlyPostBack request. Perhaps, you can use your method to delay Refresh function in WebScheduler. By doing this, WebScheduler's bound method won't be interrupted by our client side event. I will try to inform our developer team regarding this problematic behavior. Hope this helps.

Regards,
Bernard

Hi Frank,

Have you tried this code in OnCalendarCellClicked client side event?

function OnCalendarCellClicked(controlId, cellElement, selectedDate) {    var scheduler = ISGetObject(controlId);
    scheduler.Refresh();
}

With this function WebScheduler will be forced to refresh all data in their cache. Please let me know if this function solved your problem. Hope this helps.

Regards,
Bernard

Posted: May 15, 2014 10:54 PM

Hi su su,

Our WebGrid 6, could run properly in IE8 and IE9 when you're using XHTML or HTML4 doctype. Is there any simple sample or any steps to replicate you issue in our local end? Perhaps, you can give me your aspx page so I can check your sample here. This will help us to determine where the problem comes from. Please also let me know WebGrid version that you used to replicate this issue. I will look forward to hearing any feedback from you.

Regards,
Bernard

Hi Jean,

I can replicate your issue in our local end. I have made this issue as Work item and the hotfix for this issue will be added in our hotfix release by the end of this month. We are really sorry for this inconvenience. Hope this helps.

Regards,
Bernard

Posted: May 13, 2014 9:57 PM
Hi Raj,

I think this issue will be fixed in the end of this month because this issue has been stacked in our developer work task. I will let you know if there are any hotfix regarding to this issue.

Regards,
Bernard
Posted: May 6, 2014 4:46 AM
Hi Adelhard,

Perhaps this issue happen because there are browser issue in IE. This issue happen because some of our API need parentNode of specific HTML element which created by WebCombo Initialize function. Unfortunately, some API in IE deny our API to get that parentNode which causing our javascript to break. Perhaps, to resolve this issue, you could send the value to client side to be set in WebCombo. You can download our sample here. Hope this helps.

Regards,
Bernard
Posted: May 6, 2014 12:41 AM

Hi Daniel,

Regarding to this work item, this work item still on progress in developer work task. I will let you know if there are hotfix to fix this issue from our developer team. I also have put this issue as critical issue so they will fix this issue as soon as possible. Hope this helps.

Regards,
Bernard

Posted: May 5, 2014 2:40 AM

Hi Kveta Nemcova,

I can replicate your issue in our local end. I have made this issue as work item and I also have pushed this issue to our developer team for further investigation. We are really sorry for this inconvenience and I will let you know if there are any hotfix regarding this issue in the future.

Regards,
Bernard

All times are GMT -5. The time now is 4:57 PM.
Previous Next