Hi,
Is there any way to change the field position by code in the field layout?.
The ActualPosition property is read only and changing the Column property has not effect... I guess that the ActualPosition property as priority over the Column property.
Anyone?
Thanks.
Hello sebl,
The FieldCollection object inherits an ObservableCollection<Field>. You can utilize the ObservableCollection's Move() method to accomplish what you are looking for. For example:
grid.FieldLayouts[0].Fields.Move(1, 0);
The two integer parameters are the oldIndex and newIndex, respectively.
For more information, you can see the documentation here.
OK,
This does allow me to change the index of the field, but the property ActualPosition is still the one that seems to be used when displaying the fields.
In the end, all fields remain at their current position.
Please take a look at this sample project.
With the first button you move the field and with the second one, you check the actual position of one of the fields.
Feel free to let me know where you have problems or where you see an unexpected behavior.
Regards,
Alex.
I think I found out what the problem is. You can reproduce it in your sample as well.
As soon as you move a column by drag&drop, you can't change the position of a field anymore programmatically.
In my application, I allow to hide a column by right clicking on the header. When the user tries to bring it back, I try to move it at the end of the FieldCollection. Since it doesn't work, I guess that setting the Visibility flag to collapsed on a field of the FieldLayout produces the same kind of problem.
It doesn't work because of a call to LoadCustomizations. I can hide columns and I will still be able to move columns around by code, but I soon as I call LoadCustomizations or if I move a column by drag&drop, I can't do it anymore.
Actually, I can reproduce this without calling the LoadCustomizations method. I believe this could be a possible issue. I am going to investigate this and follow-up here.
OK, Thanks. I hope there is some kind of workaround.
What I was saying is that you can reproduce the problem by either changing a column's position by Drag&Drop OR calling LoadCustomizations.
I will create a support case on your behalf and link it to this issue. There is a way around this. The Column, Row properties are not take into consideration if the user has moved,fixed, loaded customizations. That is why you have to call the ClearCustomizations() method. Here is one option that you have:
xamDataGrid1.ClearCustomizations(
CustomizationType.FieldPosition);
FieldCollection fields = xamDataGrid1.FieldLayouts[0].Fields;
fields.Move(0, 3);
Regards,Alex.
Hello Ankit,
I can say that the firing of the events is normal, because our controls doesn’t fire them if the action is done by code. If so, you can execute the desired code after the action you perform. This is like a pattern for custom controls, which is used to have better performance.
Hope this helps you.
Stefan,
For throwing more light on the requirement, this will explain what I really want:
-The "FieldPositionChanged/Changing" event is fired only when user drag/drop columns in the grid.(As far as the documention in your website is concerned).
-I am hoping that is correct, in that case, I want to achieve all the column's position information even after I have changed the columns by some other means.
For Eg, I changed the collection and bind it accordingly to the grid. In this case, even if the ActualPosition would have changed for each column, but the FieldPositionChanged event would not fire, and thereby I would not get the details to save the layout, in which case, while loading the same layout, the column order would be intermittent.
-Can you suggest me some solution for the above wired scenario. I would be very grateful to you.
Thanks,
Ankit Srivastava
Now, All I want is a property which is fired whenever any fields in the dataGrid changes its position, so that I can fire the FieldPositionChangedEvent and get the XML file with field's position information.
This works fine in the scenario where I an dragging and dropping the columns and then calling SaveCustomization().
But in between the two steps, I am adding one more step which is:
-Managing columns which shows the columns you want to add or remove, after doing that when I am hitting OK, in the back-ground I am clearing the customization with FieldPosition to accomodate the changes.
-And then I hit to SaveCustomization. I guess this is the reason why the XML doesn't gets the attribute's value for ActualPosition(ColSpan,RowSpan,Row,Column)
Is there a way in which we can save the customizations.
Thank you for your post. I have been looking into it and I and I created a sample project for you following your scenario and everything seems to work ok on my side. If the sample doesn’t satisfies all your needs feel free to modify it, so it reproduces your behavior and send it back to me for further investigation. I tested the project both with the RTM and latest Service Release of version 11.1.
Looking forward for your reply.