Jan 24, 2017, 9:31 PM
Hello!
I'm sorry the integration of the solution didn't really work on the actual application.
Maybe it just didn't export App.direct? Or maybe you are using a different namespace for direct methods (or the application at all)?
There are two possible causes the direct method be missing on your page:
1: you didn't add the DirectMethod attribute (line 6 of the main page on last post from me)
2: you defined a different namespace on your resource manager so that components on client-side are accessible with YourNamespace.QuickSearch instead of App.QuickSearch. In this case, line 18 of the custom control should read YourNamespace.direct instead of App.direct.
If that's a possibility on your production scenario, please give it a try. You can also change line 18 mentioned above to something like:
Hope this helps!
I'm sorry the integration of the solution didn't really work on the actual application.
Maybe it just didn't export App.direct? Or maybe you are using a different namespace for direct methods (or the application at all)?
There are two possible causes the direct method be missing on your page:
1: you didn't add the DirectMethod attribute (line 6 of the main page on last post from me)
2: you defined a different namespace on your resource manager so that components on client-side are accessible with YourNamespace.QuickSearch instead of App.QuickSearch. In this case, line 18 of the custom control should read YourNamespace.direct instead of App.direct.
If that's a possibility on your production scenario, please give it a try. You can also change line 18 mentioned above to something like:
<Select Handler="App.direct.QuickSearch_Selected('testing');" />
So that it will just break if App.direct is not defined. You can double-check the effective namespace on a page calling Ext.net.ResourceMgr.ns. It is a string that by default would contain App.Hope this helps!