Hi,
A few questions:
1) If we don't supply the HeaderText for a column it automatically uses the Key as HeaderText. Can this be disabled? We now use a space as HeaderText to prevent the Key from being used. The Key as HeaderText is not really a wishful scenario, only when AutoGenerateColumns is enabled...
2) If I set the width of a column to * and the minimum width to 100, when the grid columns are wider than the available space, my star column will be collapsed further than the specified minimum width. Is this a bug?
3) When I clear the FilteringSettings.RowFiltersCollection the original itemssource is restored, but the filter options remain, is there anyway to reset them also?
4) Multiple column sorting is done by holding the ctrl key, in Windows Explorer this is done by holding the shift key. Could you make an option to specify which key can be used to sort multiple columns?
5) We found the latest SR (21 oct.), but we didn't find any sourcecode with that. Where can we get the latest source code?
Thanks,
Arjen
Hey Arjen,
I just got confirmation that the 9.1 SR Source has been posted to the website.
-SteveZ
Hi Steve,
1) It's not problematic, it's just strange to specify a space when you don't want a HeaderText :)
3) Setting FilteringSettings.FilterScope to ColumnLayout did it.
Hi Arjen,
1. Its not currently on our Feature List. Although i am curious, is the workaround of setting the HeaderText to a space problematic? As another workaround, you set the HeaderTemplate on the Grid level, to basically an empty TextBlock. However, you'd then need to set the text of the header for Columns that you do want text for.
this.xamWebGrid.ColumnsHeaderTemplate = Resources["emtptyHeaderTemplate"] as DataTemplate;
3. That FilterCellValue is only used when grid.FilteringSettings.FilterScope is set to ColumnLayout. My guess is that you're not doing filtering on childbands for this scenario, so this would actually be the type of Scope that you'd want to set.
Thanks for the reply.
1) So this also won't be a feature in the future?
2) Ok
3) col.FilterColumnSettings.FilterCellValue seems to remain null if it is filled. Also setting it to null does not have effect...
4) Nice!
5) Ok
Thanks!
1. No this feature cannot be disabled.
2. Yes this is a bug, where i completely overlooked this behavior for Columns with a * width.
3. You'll need to clear the FitlerCellValue off of the FilterColumnSettings of a Column:col.FilterColumnSettings.FilterCellValue = null;
4. Yes, we can/will definitely add this feature.
5. Thank you for pointing this out. We just overlooked putting it on the website. As soon as we add it, i'll reply to the post to let you know.
Thanks for the feedback,