I have several grid, stacked on ne another. I want certain attributes to remain in synch with the other. For example, if I create a new Col Scroll Region, I want the other grids to have the same a new Col Scroll Region as well.
In the handler for the event, is there a way I can tell the other grids to perform the same action as was done on the first grid? So, in the above example, can I tell the other grids "perform user action" i.e. drag the "splitter" on the two grids to open a new Col Scroll Region.
Thanks!
Well, if you are asking if there is some generic way to tell one grid to perform the same action that another grid did, then the answer is no.
You can, of course, handle the events of one grid and programmatically change another grid to be the same. For example, when a ColScrollRegion is created, you can call the split method on the ColScrollRegion in the second grid and create a split that is the same size.
Thanks Mike! What you suggest (Split(), etc) is what I am currently implemented. But my code would be simplied if I could do something similar to what to what is talked about in the link -> http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.Aspx?ArticleID=1004
So the code would make the other grids simulate user action. In other words, it would be similar to the user performing the same action for each grid individually. Is that possible for scroll region resize?
Hi VRN
Yah, i got the same behavior. But i could not find a solution to that. Let me know if you solved that problem.
Navi
Navi, thank you so much for your suggestion.
In the past I have seen another implementation using the "Position" property where the "follower" grid behaves in jerky fashion. As the "leader" grid scroll bar is dragged to the new position, I saw the "follower grid" not following along but just jump to that new position when I let go of the "leader" grid's scroll bar. Did you get this behavior too?
Hi
I hope the link below will help
http://forums.infragistics.com/forums/p/9852/37939.aspx#37939
This article refers to keyboard interaction with the grid. Since scroll regions are split using the mouse, not the keyboard, this method cannot be applied here.