Yes, we're on build 431 of ISNet.WebUI.WebGrid.dll.  Please note that we do NOT use the built-in row checker due to the check box not fitting into our UI, but I will try the hotfix and let you know how that works.  Thank you.

We're also running into the slow script issue.  It only happens under certain conditions but am not sure why.  It only seems to happen when we initially load certain grids.  We use IE8.  I used the developer tools to stop the script so I can see where in the code it's stopping as the source of the issue and it's stopping inside the dotfuscated code here at the for loop line (I included the Array line for your reference):

...
var v5fc40 =new Array("gridId","tblName","subId","tblLevel","colName","noEdit", "keyValue","relNames","recordIndex","parentGroupIndex","hasParent","isGrouped", "isSorted","groupIndex","sortOrder","parentIndex","childrenLoaded","fullPath", "filterText","filterType","oldText","oldCellValue","srRC","srLevel", "parentValue","csRowPos","rowChecker","cellValue","isRowChecked","childNotExpandable"); for (var vcda60=0; vcda60<v5fc40.length; vcda60++)
...

Our pages use the following:

I'm not sure what the final solution is for IE8 due to the length of this thread.  Any chance you can summarize the solution please?  We need to have this fixed as we're planning a production build soon and can't release it with this issue.  Thank you.

I wanted to voice my irritation with your phone support.  We just upgraded to 2011 R1 and even though everything is installed and registered, we're still getting the "you are evaluating" this product message.  I called last week and asked for someone to help us resolve this and was told someone will call back no one did.

I tried to follow up this afternoon and got nowhere.  The first time I was transferred into a non-English speaking mail box.  Then the two calls after I was transferred to an abyss where I just got a dial tone.  With every call I became more irritiated because the lady on the other side is rude and unprofessional and can't seem to understand that we're paying to get the support service and don't need the additional aggravation of having to call back constantly because she can't transfer a call properly.  And when I tried to explain my aggravation she constantly put me on hold and spoke over me.  That's three calls and I was NOT able to even leave a voice message for anyone.

When I asked to speak to her supervisor she said no supervisor was available.  I will follow up with a supervisor later today or first thing tomorrow morning.  I'm not sure what the point of this phone number is because every time I've tried to use it, it's been nothing but a hassle.  This forum has been more helpful than trying to reach your folks via this number.  I hope you can fix this issue.

Am I the only in the US experiencing this frustration?  I would love to hear from others and your experience using this support number to get help.  Thank you.

Why does the grid crash when we use the built-in operator and condition but works when we use the custom condition for Boolean and Int types?

If we set a custom condition of "underline=1" this works fine.

If we set the TargetColumnMember to "underline", set Operator to ColumnFiltertype.EqualTo and set ConditionText to "1" the grid crashes upon rendering which doesn't make any sense.  The same thing happens if we use an Int where the value is other than 0 or 1.  Any ideas?  At least the workaround of using the custom condition text is working right now.

I think we have this figured out.  It looks like we can use the row-based conditional formatting to add the border we need based on a hidden value.

The one thing, during testing, that I noticed is that using a target column to check equal to a string value doesn't seem to work.  We wind up using the custom condition text to set up a formula, e.g.,

ISNet.WebUI.WebGrid.WebGridFormatCondition fmt = new ISNet.WebUI.WebGrid.WebGridFormatCondition();
fmt.Name = "RowConditional1";
fmt.TargetObject = ISNet.WebUI.WebGrid.TargetObjectType.Row;
fmt.CustomConditionText = "testTargetColumn = 'String Value'";
fmt.Operator = ColumnFilterType.NotSet;
fmt.FormatStyle.BorderSettings.Bottom.Color = System.Drawing.Color.Gray;
fmt.FormatStyle.BorderSettings.Bottom.Style = BorderStyle.Solid;
fmt.FormatStyle.BorderSettings.Bottom.Width = Unit.Pixel(1);
fmt.Enabled = true;

this.RootTable.FormatConditions.Add(fmt);