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
We did upgrade from WebGrid v6 to WebGrid v7. Our custom js file used
'WGMenuEngine' variable which was declared in 'CommonLibrary\WebGrid\V6_0_7200
\WebGrid_Context.js'.In v7 you have stoped to use 'WGMenuEngine' variable and as a result our
javascript code is broken (see code below). My question is, how in WebGrid v7 to
point to the WGMenuEngine object which supposedly is a ColumnContextmenu
Our broken code: //WGMenuEngine undefined
if (WGMenuEngine) { try { mnuFunc = WGMenuEngine.FilterMenuApplyAll; WGMenuEngine.FilterMenuApplyAll = fnFilterMnuClick; mnuClearFunc = WGMenuEngine.FilterMenuClearAll; WGMenuEngine.FilterMenuClearAll = fnFilterMenuClear; mnuClearThisFunc = WGMenuEngine.FilterMenuClearThis; WGMenuEngine.FilterMenuClearThis = fnFilterMenuClearThis; } catch (err) { } }
Hello,
WebGrid 7 obfuscates the internal engines. That's why you could not access it anymore. In WebGrid 7, we enhanced WebGrid to handle Column Context Menu. You can customize it also for Filter menu. Almost all context menu can be customized/acessed now. So, I don't think you need to use your own .js now.
Regards,Handy
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