Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FilterHeader plug in removed by grid.reconfigure(columns) #1572

Closed
fabriciomurta opened this issue Dec 20, 2017 · 1 comment
Closed

FilterHeader plug in removed by grid.reconfigure(columns) #1572

fabriciomurta opened this issue Dec 20, 2017 · 1 comment
Assignees
Milestone

Comments

@fabriciomurta
Copy link
Contributor

Found: 4.5.0
Ext.NET forum thread: filter header disappeared after reconfig with new cols

When a grid with filter headers is reset via the grid panel's reconfigure(columns) call (when you specify the new columns to reconfigure the grid with), the filter header fields are not added to the column title.

After the reconfigure (or before) calling grid methods to add columns works correctly and the field is introduced correctly.

@fabriciomurta fabriciomurta added this to the 4.5.1 milestone Jan 4, 2018
@fabriciomurta fabriciomurta self-assigned this Jan 4, 2018
@fabriciomurta
Copy link
Contributor Author

Just as a side note, for Ext.NET MVC, just getting a grid from a direct event/method wouldn't make it so code behind knows about the grid having the FilterHeader plugin, so even AddColumn() and InsertColumn() will not craft the column object to include the right fields. In such situations where the grid is retrived via X.GetCmp(), the FilterHeader plug in should be reattached to the grid object for the side effects to take place, for example:

var grid = X.GetCmp<GridPanel>("GridPanel1");
grid.Plugins.Add(new FilterHeader());

This is a limitation from MVC, not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant