Is there a way to set up the ultrawingrid (on a windows form, vb.net 2.0, windows xp) so that the active row and selected row are always the same? It is confusing to my users when a row is highlighted and then they click on another row and that becomes the active row, but it is not selected.
Thanks,
Hello Saurabh,
Your question here is duplicate with your questions in these froum threads:
http://es.infragistics.com/community/forums/p/24260/431012.aspx#431012
http://es.infragistics.com/community/forums/p/40334/431966.aspx#431966
Please take a look there for more details
Hi Mike,
I am a ultragrid that has more than 200 records. and we are using hyperlink for one of the column in grid.
I have a scrollbar on ultragrid to see more records on grid which are not fit in grid.
Now when user is trying to click on hyperlink of last row (not grid last row) in the section which is visible so it moves focus from there so it's difficult to user to click on hyperlink which is on visible last row. this issue is repeatable even there is no hyperlink but if user clicks on row.
Mike,
I had considered that based on your earlier recommendation. But in my case, as soon as I change all of my logic to look at the active row instead of the selected row, 'THEY' will tell me to allow multiple rows to be selected. If I knew for sure they would never ask for multiple rows I would definitely use your recommendation.
-bob
If you only want the user to be dealing with one row at a time, then what I usually do is turn off row selection entirely and then just always deal with the active row.
grid.DisplayLayout.Override.SelectTypeRow = None
I had a similar problem, I only wanted the user to see the selected row hilighted (i.e., very easy to end up with 1 row selected and a different row active).
Originally I just set ActiveRow to null in _AfterSelectChange. Later I found this caused a NullReferenceException when I tried to group rows by a column (took me awhile to figure out the culprit).
My Solution: Now I'm setting .ActiveRow = .Selected.Rows[0]. in _AfterSelectChange. I didn't want to convert everything to use the ActiveRow, because I foresee "them" requesting the ability to perform actions on multiple rows in the future.