Hello @lousberg! Thanks for the test case!
Option 1: Exclude what's inside the paging toolbar:
item.isDirty && item.isDirty() && !item.up().is('pagingtoolbar')
Option 2: Use
ext:FormPanel instead of
ext:Container!
Then you check if the form panel is dirty; it will traverse any form fields within it to check whether they have been changed since load or last commit!.. Well, and the grid panel (or probably panels) you have, then you can use a selector just for them. Here's your test case with a bit of expansion with what I believe you may have (like fields within fields, and an assortment of grid panels).
<%@ Page Language="C#" %>
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
if (!X.IsAjaxRequest)
{
this.BindData();
}
}
private void BindData()
{
Store store = this.GridPanel1.GetStore();
store.DataSource = this.Data;
store.DataBind();
}
private object[] Data
{
get
{
return new object[]
{
new object[] { "3m Co" },
new object[] { "Alcoa Inc"},
};
}
}
</script>
<!DOCTYPE html>
<html>
<head runat="server">
<title>63165 - Grid with Paging Toolbar Dirty flag</title>
<script>
var hasDirtyChild = function () {
var cont = App.container1;
var ret = false;
if (cont.isDirty()) {
ret = true;
Ext.toast("Form panel is dirty.");
}
Ext.each(cont.query('gridpanel'), function (item) {
if (item.getStore().isDirty()) {
ret = true;
Ext.toast('Dirty: ' + item.id);
}
});
if (!ret) Ext.toast('All clean.');
}
</script>
</head>
<body>
<ext:ResourceManager runat="server" />
<ext:FormPanel runat="server" ItemID="container1" ID="container1">
<Items>
<ext:TextField runat="server" FieldLabel="Name" Text="Alex" />
<ext:TextField runat="server" FieldLabel="Address" Text="Their street" />
<ext:FieldSet runat="server" Title="Sub items">
<Items>
<ext:TextField runat="server" FieldLabel="Item 1" Text="Value 1" />
<ext:TextField runat="server" FieldLabel="Item 2" Text="Value 2" />
<ext:TextField runat="server" FieldLabel="Item 3" Text="Value 3" />
</Items>
</ext:FieldSet>
<ext:NumberField runat="server" FieldLabel="Amount" Text="7" />
<ext:Checkbox runat="server" FieldLabel="Is ready" Text="false" />
<ext:GridPanel
ID="GridPanel1"
runat="server"
Title="Array Grid"
Width="800">
<Store>
<ext:Store ID="Store1" runat="server" PageSize="10">
<Model>
<ext:Model runat="server">
<Fields>
<ext:ModelField Name="company" />
</Fields>
</ext:Model>
</Model>
</ext:Store>
</Store>
<ColumnModel runat="server">
<Columns>
<ext:RowNumbererColumn runat="server" Width="35" />
<ext:Column runat="server" Text="Company" DataIndex="company" Flex="1">
<Editor>
<ext:TextField runat="server" />
</Editor>
</ext:Column>
</Columns>
</ColumnModel>
<BottomBar>
<ext:PagingToolbar runat="server">
<Items>
</Items>
</ext:PagingToolbar>
</BottomBar>
<Plugins>
<ext:CellEditing runat="server" />
</Plugins>
</ext:GridPanel>
<ext:Button runat="server" Text="Check Dirty" >
<Listeners>
<Click fn="hasDirtyChild"></Click>
</Listeners>
</ext:Button>
</Items>
</ext:FormPanel>
</body>
</html>
Okay, I haven't really included the
assortment of grid panels here, I think it would just make the sample long; we use the selector to find grid panels and it may be enough -- as long as you are nesting the grid panels within the
container1 (which I kept the ID despite changing into a
FormPanel).
These are not the only options; you can also fancy an advanced
Ext.ComponentQuery to the container and make the selection excluding whatever else may be getting misleading dirty values... Well, and who knows what else could be done for that goal... I am just showing a few options that came to mind.
In case you are wondering why the number field in the paging toolbar is becoming "dirty" although you didn't change it, the answer is, Ext.NET changes it on load. It may not be exactly this, but roughly, the page counter is initially empty and the paging logic fills them as it determines the amount of pages and ensures it is in the first one. Paging toolbar is designed for remote data and although it looks very simple with Ext.NET code, a considerable amount of sugar has been added to the syntax (and extensions) to make that possible. So it never loses its "dynamic" aspect.
Hope this helps!
