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
Hello,
I'm using client side OnAfterValueChanged event and I have noticed that this event is firing twice. Just wander if this is a bug or I’m doing something wrong. I'm providing sample code which demonstrate that issue. I would appreciate solution or work around if possible.
Thank you
Hi Mark,
Thank you for the sample. I have tested your sample and enable to reproduce the issue. I have forwarded this issue to our WebInput Development Team. I will inform you for any news in this thread.
Regards,
Julia
Thank you Julia. What is time frame to resolve this issue? I have number of input controls which require that event to work properly. My project release deadline is approaching fast. I would appreciate fix asap.
Thank you in advance
Mark
I'm apologize for the delay answer. Currently our development team is investigating this project. I haven't receive any confirmation on when the hotfix will be ready. If you don't mind, may I know the deadline of your project?
Project is going to QA this Friday (Apr 23rd). So i hope you understand the rush.
I'm sorry to keep you waiting. I have created a workaround for you based on the sample that you attached before.
As the mask of WebInput has edit text and display text, you will have two different values for every new input value. Apparently, this two value that might be triggered the OnAfterValueChanged event twice. So, to avoid the event being fired twice, we need to compare if the new value is really come from user and not by mask. It is a little hard if the comparison value has different format of slash and dash. So by using regex, we could manipulate to equate the edit value as display value, this way the event wouldn't do more firing.
For more detail, here is the attachment of my workaround.
Please let me know if this workaround could help or not.
Hi Julia,
Thanks for the workaround. Unfortunately it does not work for me. Event is still firing twice. I will not spend more time on it. I will go with the simpler (cheap) workaround . But I still think this control should be fixed permanently without the need for workaround.
Thanks
}
Thank you for sharing the workaround with us. I have forwarded your valuable feedback to our development team. Please let us know if you need another help.
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