upgrade from WebGrid v6 to WebGrid v7. JavaScript code is broken

handy@intersoftpt.com — Tue, 23 Mar 2010 23:48:38 GMT

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

upgrade from WebGrid v6 to WebGrid v7. JavaScript code is broken

NK1958 — Tue, 23 Mar 2010 17:47:54 GMT

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) {
        }
    }

Intersoft Community - WebGrid Enterprise - upgrade from WebGrid v6 to WebGrid v7. JavaScript code is broken

upgrade from WebGrid v6 to WebGrid v7. JavaScript code is broken

upgrade from WebGrid v6 to WebGrid v7. JavaScript code is broken