What is the best way to programmatically select all rows in the ultragrid grid?
According to Infragistics, (http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=6546) this is the best approach:
In C#
this.ultraGrid1.Selected.Rows.AddRange((UltraGridRow[])this.ultraGrid1.Rows.All); |
In VB
Me.UltraGrid1.Selected.Rows.AddRange(CType(Me.UltraGrid1.Rows.All, UltraGridRow())) |
Has anyone had any luck converting this code to Progress? I'm assuming it's something simple that I'm missing but I haven't found it yet.
TIA
Progress 10.2A, GUI for .NET
Not sure if this is the *best* way, but...
Select all:
Deselect all:
Hope this helps.
You should simply be able to do the below. Unfortunately there's a bug (logged) which prevents you from doing so.
using Infragistics.Win.UltraWinGrid.*.
ultraGrid1:Selected:Rows:AddRange(cast(ultraGrid1:Rows:All,"UltraGridRow[]")).
So while that may be more informative than actually useful at this time, I thought it'd be good to know for future reference.
-- peter
Peter,
When I add your sample code is does not compile.
THIS-OBJECT:gridItem:Selected:Rows:AddRange(CAST (THIS-OBJECT:gridItem:Rows:All, UltraGridRow[] ) ).
Roger, did you miss the part where he said "Unfortunately there's a bug (logged) which prevents you from doing so."
Apparently so. Reviewing the thread on a Blackberry is sometimes difficult to do. Thanks for the comment and clarification.
You should simply be able to do the below. Unfortunately there's a bug (logged) which prevents you from doing so.
Peter, any info when that issue will be fixed?
Apparently so. Reviewing the thread on a Blackberry is sometimes difficult to do. Thanks for the comment and clarification.
That may be challenging. But what works pretty nicely now is to reply to a thread from a mobile phone (iPhone) using the reply via email function.
I wish someone officially announced that as a new feature of the board software rather than letting us try it out.
Hey, thanks...pretty cool.
Peter, any info when that issue will be fixed?
All indications are that OE00186347 will be fixed in 10.2B.
-- peter