Search found 6 matches

There is a bug where adding records to filtered tree stores, and then unfiltering the store, causes the record to completely disappear. After diving in some more, I've noticed that this happens because the new record isn't added to the rootNode's unfilteredChildren collection, which then causes it t...
Pavel, Thanks for these. However, both of these approaches seem to create a new store for every new combobox instance. Isn't this a lot of overhead, especially for larger stores and as the number of comboboxes increases? In Ext.JS, I believe it was sufficient to use a single shared store across mult...
If there are multiple comboboxes and the same store is reused across all of them, combo filtering will fail to work for one or more of the comboboxes. This is reproducible - the code below will render 2 combos, but only the second one will filter correctly: var testStore = new bryntum.scheduler.Stor...
There is a bug with filtering columns in tree grids. After filtering a column in a tree grid and getting no results, refiltering for a substring of that value will also fail to return any results even though valid matches exist. If the user completely clears the filter (by hitting 'x' or backspacing...
Is there a way to selectively turn off cell editing for specific columns, based on the row record? For example if the row's record ID is 52, then columns B, C and E cannot be edited, etc. I do see that there might be a way to do this by subclassing the Column class and overriding canEdit(), but I'd ...