Hi Jason,

     There is nothing specific that I can think of that would cause that, except for rather specific settings. Two are in Tools-> Options, GUI Testing -Test Runs, Run mode, make sure it's set to Fast, that is the default, but if you set it at some point to something else, it stays. The other being Active Screen, typically it affects recording, and affects WPF and Web, more than Winforms, but it may affect Debug as well. Set it to Capture level None. 
   We have some internal wait settings in IG TestAutomation, proxy settings that allow you to raise the wait time, but unless it's in your script or you actively changed it in your swfconfig, most of them default to zero, with one at 0.125 seconds, but that is only for exception retries, to allow for proper repainting. If you set those settings in Winforms via the SetProxySetting method in your script, the lifecycle for that setting is for the playing of the script.

   That being said, there is nothing on our end that would cause the slow down that you are experiencing. Do you get a big difference between Run from step and Debug from step, and commenting out everything before that point and just hitting run. If you get a big difference between those than my guess the issue is on HP's side and how they load assemblies, what they inject themselves into and collisions that may occur based on that when they go into to "Debug" mode.

Michael Germann
Software Development Team Lead
Infragistics

Hi Kirtee,  Well that depends, are you wanting to look at a specific Cell’s value. You can do that with the GetCellData method. This will return the value, the parameters you pass in are identical to that of SetCellData, but without the new value. This will work if you know which cell is orange, and just want to verify it. If you want to verify if a cell is orange you would need to use the GetCellAppearance method. Again the identification of the cell portion is identical to SetCellData, but it adds a Appearance enumeration property to identify what appearnace you want to return. Note how UFT works to return values from a method you need to put parenthesis around the parameters. So if your SetCellData was:SwfWindow(“Form1”).SwfTable(“ultraGrid1”).SetCellData “2”, “Name”, “Jim Bean” name = SwfWindow(“Form1”).SwfTable(“ultraGrid1”).GetCellData(“2”, “Name”)

similarly you can do :textColor = SwfWindow(“Form1”).SwfTable(“ultraGrid1”).GetCellAppearance(“2”, “Name”, appForeColor)backColor = SwfWindow(“Form1”).SwfTable(“ultraGrid1”).GetCellAppearance(“2”, “Name”, appBackColor)Hope this helps,

Michael GermannSoftware Development Team LeadInfragistics

Hi Greycon,

    Short answer, unfortunately is no. I pinged it with both the developer of the control and of our CodedUI support for the control, and they both agreed it is not feasible. It would be a mix of changing the underlyng framework of the control, to support it, then the implementing of the pattern would be measured in months in the initial estimate to properly implement it.

Sincerely.

Hi Oyvind,

    OK, I do see the issue, and unfortunately it is not built into the UltraSpellChecker to handle that scenario directly. There are several workarounds viable, you can implement your own SpellCheckerDialog that inherits from SpellCheckerDialogBase, and on the SpellCheckDialogOpening replace the dialog with your own. You should instead be able to on the SpellCheckDialogOpening access the exist SpellCheckForm, and hook into the ChangeAll button event, from there you could either loop through the controls or just add the values to a local dictionary, which before you proceed to the next control loop through the values in the dictionary and replace the exist text, then call the spellcheck.

 void spellChecker_SpellCheckDialogOpening(object sender, SpellCheckDialogOpeningEventArgs e)
{
            UltraButton btnChangeAll = e.SpellCheckDialog.Controls.Find("btChangeAll", true).First() as UltraButton;
            btnChangeAll.Click += btnChangeAll_Click;
}
void spellChecker_SpellCheckDialogClosed(object sender, SpellCheckDialogClosedEventArgs e)
{
            UltraButton btnChangeAll = e.SpellCheckDialog.Controls.Find("btChangeAll", true).First() as UltraButton;
             btnChangeAll.Click -= btnChangeAll_Click;
}

You can also submit your feature idea and track it's progress on product ideas page here : http://ideas.infragistics.com/

Hope this helps,

Hi Oyvind,

    I just want to clarify what you mean by the scope here. I get several interpretations of scope from what you wrote each significantly different.
Do you want it to update every control's instance of the word, not just the current word?
Do you want it to auto-update future instances of the word?
    If this is the case, when would you expect to do it? Only when the spell checker is opened, or after the word is typed?

Or is it something else?

Michael Germann
Senior Software Developer
Infragistics

Hi Srinivas, 
   The error doesn't seem to make sense with the line of code that you are showing. I am going to assume that the checkbox column in the picture is the "SELECT" column, and the data type for that column is boolean as you are sending a value of True. Which is neither a string or a decimal.

   My thoughts would be one the error is actually internal to your application, and the reason it may not be reproducible via the UI is the events may be triggered differently when using SetCellData then manually doing it via the UI. This sometimes happens if a developer listens to a mouse based event instead of or inconjunction with the CellChanged and\or one of the Update events. This is because we update the cell's data directly and which triggers the changed and updates event and not the individual mouse events. 

The other idea is that the error may be for another line of code. Either way can you include the image for the error message, sometimes there is additional information in the error message that we can interpret the root cause. 

One final code was the line of script above hand scripted or recorded?

SetView is an action for the XtraGrid, which is a DevExpress grid. As this is an Infragistics site, we won't have the best information on the subject. I would recommend contacting HP as they created the support for the XtraGrid.