Hi, Is their a way to limit a user to only have one row of fields/columns? The problem I have is I have a very advanced field picker which I also use for ordering but the ability to have two fields in the same column (different row) is causing me a real pain and not something the users want anyway. I tried to hook into the FieldPositionChanging event and cancle it if 0 != row but unfortunatly the developer didn't think to actually tell me where the field was moving to only where it is now so this is useless. The changed event is a little to late in the day to do anything.
Thanks
Muumi
Thanks for looking into this. In my case this is insufficient because you can only specifcy to guard either rows or columns. What if you need something more flexible? The current implementation just doesn't provide enough information.
The presence of the enumeration just highlights the fact that internally the data presenter has all the information it needs to expose the proposed column and row index of a field in the event args before a field is moved.
Hello,
I have been looking into your requirement and can suggest you set the AllowFieldMoving property to WithinLogicalRow in order to prevent the users from creating their multirow columns. Here is a code snippet you can test out:
<igDP:XamDataGrid Name="xamDataGrid1" BindToSampleData="True" >
<igDP:XamDataGrid.FieldLayoutSettings>
<igDP:FieldLayoutSettings AllowFieldMoving="WithinLogicalRow" />
</igDP:XamDataGrid.FieldLayoutSettings>
</igDP:XamDataGrid>
Please let me know if you require any further assistance on the matter.
I'm running into this situation myself. I have to say I am not at all impressed with the XamDataGrid's implementation of field positioning.
You implemented a new feature allowing users to drag fields around into multi-row layouts which leads to a confusing and complicated field dragging UI. You didn't add any way for developers to prevent this from happening other than to flat out dissallow field dragging in the first place! To top it off, in the FieldPositionChanging event couldn't even provide the proposed destination for the new field. What's the point of a cancleable event if you don't know what you're cancelling?
I guess my main frustration is that you guys spent cycles implemting this half-baked feature and didn't bother to port over the extremely useful column grouping feature that was in the WinForms UltraWinGrid...