iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Gentlemen,
Recenty I added a client side event - OnEventBound to my websheduler as follows:
<!--
{
}
</script>
The client side event performs as intended in my code. However, when trying to add additional client side events in the webscheduler properties dialog by I am receiving a strange parameter count error, (screenshot attached).
If I remove the last two code lines from the OnEventBound client side event;
var div = evt.GetContentElement(); //** Event bar div
The parameter count error no longer exists, but my OnEventBound client side event does not function as intended.
I have no idea what is going on, can you please advise?
Thanks - Frank
Thank you for the detail step by step guide to reproduce the reported problem. I suspect that there is something wrong with the designer.
Temporarily, please do the following (before add other client side events of WebScheduler).
I will have this reported problem forwarded to WebScheduler development team to be investigated further. I’m quite sure that the problem only happens with the WebScheduler properties dialog when developer tries to add client side event.
Please let us know if you have other questions.
Yudi,
Thank you for your reply. I will look at this next week and post back the results.
Frank
Hi Yudi,
Tried the above steps and the results are as follows:
1). I can add client side events with the two lines of code REMOVED from the OnEventBound.
2). I can "manually" add client side events with the two lines of code NOT removed from the OnEventBound.
For now, I will just either add manual client side events, or remove the two lines of code, add a new event and then put the two lines of code back. The issue does not seem to affect the performance of the wescheduler control at runtime.
Thank you very much for the contribution by confirming the result.
The reported problem deals with the WebScheduler properties dialog when developer tries to add client side event but not affecting the performance of the WebScheduler control at runtime.
The development team will check what may cause the issue and fix it.
Should you need further assistance or run into technical problems regarding our controls, feel free to post it into our community site. We would be happy to assist you again.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname