Search found 65 matches

After looking at the source code for the gridfilters plugin a bit further, it looks like it stashes a reference to itself on its grid by the name "filters". This means you won't need the findPlugin() call after all: p1 = this.gantt.filters; p2 = this.gantt.findPlugin('gridfilters'); p1 ===...

How did you implement switching between states? Does it require a page reload or is there some logic in your app to reconfigure the widget on-the-fly?

The method would be found on the prototype object... You can expand that in the debugger or check:

p = this.gantt.plugins.find(r => r.$className === 'Ext.grid.filters.Filters'))
p.addFilter

(with a capital "F")

I suspect the reason you get the error "addFilter is not a function" is because you've got the wrong object. I do not see any great identifying properties on the gridfilters plugin instance that would help you know for sure you have the right one other than the undocumented "$classNam...

To synchronize your FDO toggle from the menu, you'll probably need to listen for the checkchange event https://docs.sencha.com/extjs/6.2.0/classic/Ext.menu.CheckItem.html#event-checkchange

The Ext JS gridfilters plugin does not use the store's filters to determine its presentation but works in the reverse direction. The UI controls adding and removing filters from the store. Ext JS has no documented way that I can see to cooperate with these menus and check states, but the column comp...
You mentioned this happens in one of the Bryntum demos... could you drop a link to where you saw this issue? I've checked out the Filtering (https://bryntum.com/products/gantt/examples/filterbar/) and Advanced Filtering (https://bryntum.com/products/gantt/examples/fieldfilters/) demos but they do no...
There is also code in review to add tabIndex to Button - https://github.com/bryntum/support/issues/8166 As noted, adding this config to Widget is problematic. For all the reasons above plus there are many ways in which derived-class widgets manage their focusability and tabbability that would confli...
I've opened a ticket (https://github.com/bryntum/support/issues/6274) to investigate this. It appears specifically to come from mouse interaction with the range slider in the Zoom popup menu. Interaction with other elements in the menu does not cause the issue, and keyboard interaction with the rang...
I am checking into this. The issue seems to be that the Ext JS event publisher looses track of the pointer up event for the Bryntum menu and then every pointer move thereafter publisher attempts to mimic the missed pointer up. Pretty clearly an Ext JS bug but one that seems to be triggered by an eve...