I have a grid with two column scroll regions and Row Selectors enabled. However, I only want the Row Selectors to appear in the first scroll region (this would also ensure that he column chooser icon was only displayed once).
I've tried turning off Row Selectors using the following code but it removes them for the whole grid:
MyGrid.DisplayLayout.ColScrollRegions(1).Layout.Override.RowSelectors = DefaultableBoolean.False
Is there any way of removing the Row Selectors for a single Column Scroll Region?
I've also had some strange behaviour with fixed columns since adding a 2nd column scroll region. I have the first few columns in the grid set to fixed in the designer (with the push pin icon shown in the column header).
At run-time with 2 column scroll regions none of the columns are fixed (including the row selectors) and the push pin icons are not shown. If I manually close the scroll region and then create it again then all of a sudden the columns are now fixed and the push pins are shown.
I'm creating the 2nd column scrolling region in the designer if that helps.
Thanks,
John.
Hi John,
The Layout property on the ColScrollRegion is a backward pointer.
So these are the same thing:
MyGrid.DisplayLayout.ColScrollRegions(1).Layout = MyGrid.DisplayLayout
There is currently no way to make the RowSelectors exclusive to one ColScrollRegion. You should Submit a feature request to Infragistics.
henderjj said:At run-time with 2 column scroll regions none of the columns are fixed (including the row selectors) and the push pin icons are not shown. If I manually close the scroll region and then create it again then all of a sudden the columns are now fixed and the push pins are shown.
I'm not sure if the two features (ColScrollRegions and Fixed columns) were ever intended to be used together at the same time. The Fixed Columns feature was intended to replace ColScrollRegions in a much more Excel-like way.
Having said that, I tried this out by creating a new project and setting UseFixedHeaders to true. I fixed a column of columns by clicking on the pin button in the column header and then created a ColScrollRegion by dragging the splitter bar. When I run the application, it works just fine for me.
What version of the controls are you using? I'm using v10.3 with the latest service release.
Thanks for the update, I'm using 10.3.20103.2063 which I think is reasonably up to date.
I've got Use fixed Headers switched on, the Fixed Header Indicator Override set to None and then specific columns have the indicator set to Button. This is just so that by default new columns that are added to the grid at runtime won't be pinnable.
I've tried changing the Fixed Header Indicator Override to Default but it doesn't make any difference. All of my columns are set to use an Exclusive Column Scroll Region if that makes any difference.
The Fixed Headers are useful with multiple column scroll regions because it causes the row selector to be fixed as well as being able to fix a couple of special columns.
Hi,
I took a look at your sample and I am getting the same results you describe.
So I checked it out a little further and it looks like what you are trying to do here is not supported. The grid is specifically checking the column to see if it is in an ExclusiveColScrollRegion and if so, it does not allow the FixedHeaderIndicator.
Once you remove the ScrollRegion by dragging it all the way to the edge of the grid, there is only one scroll region and so therefore the ExclusiveColScrollRegion property is cleared. When you then create a new ColScrollRegion, the button shows up since the ExclusiveColScrollRegionno longer applies.
It looks like it's setting the ExclusiveColScrollRegion properties that's causing the problem. I've attached an example project that shows the problem.
The ExclusiveColScrollRegion is important since it was only after discovering this that we decided to switch from just using fixed headers to using scroll regions.
If you can post a small sample project here that demonstrates the problem, I would be happy to take a look and see what's going on. But without being able to duplicate the issue, I don't have any guess as to why that's happening.