J
Jay
Stepping through code and discoverd that an event declared for a 3rd
party datagrid (Infragistics UltraWinGrid) in InitializeComponent()
fires twice: 1 for setting its grid.dataSource, and a second time on
its grid.dataBind().
Is that correct that this happens?
What I'm investigating is a problem our QA guy is running into with
his script/tester (QTP?) and he's trying to script checking a checkbox
on that datagrid. But in certain areas his script tool bombs and in
others it doesn't. I'm almost wondering if maybe the fact that the
second call is somehow confusing the script to think it has a new
identity and "get's lost"?
In the event fire, code runs to declare a Layout and a
ColumnsCollection a second time and maybe that is the cause of the
"lost identity"? Perhaps I should look for an "IsAlreadyInitialized"
property of that grid so to conditionally step over it and see what
results that brings? Unless on dataSource and dataBind() it is
supposed to do that always?
Any thoughts would be greatly appreciated.
THANKS.
party datagrid (Infragistics UltraWinGrid) in InitializeComponent()
fires twice: 1 for setting its grid.dataSource, and a second time on
its grid.dataBind().
Is that correct that this happens?
What I'm investigating is a problem our QA guy is running into with
his script/tester (QTP?) and he's trying to script checking a checkbox
on that datagrid. But in certain areas his script tool bombs and in
others it doesn't. I'm almost wondering if maybe the fact that the
second call is somehow confusing the script to think it has a new
identity and "get's lost"?
In the event fire, code runs to declare a Layout and a
ColumnsCollection a second time and maybe that is the cause of the
"lost identity"? Perhaps I should look for an "IsAlreadyInitialized"
property of that grid so to conditionally step over it and see what
results that brings? Unless on dataSource and dataBind() it is
supposed to do that always?
Any thoughts would be greatly appreciated.
THANKS.