A few months ago i was told that there was a bug that would might be fixed soon
"As for the event not being raised, i looked into the code, and there is a bug, where it only fires for TemplateColumns that are bound to data. I have logged an issue for it, and it should be fixed in our next ServiceRelease."
Has this issue been fixed yet?
Hello,
Did you tried the July Service release. Did it fix the issue or you still need help? Just let us know?Thank you.
Sincerely,DimiDeveloper Support EngineerInfragistics, Inc.
It means we are creating the columns at runtime before binding. It sounds like the July SR will fix our problems.
The issue with the CellControlAttached for cells which are generated at runtime (not initially) should be fixed with the latest (July) Service Release.
Please, check it out, it should resolve the issue in all supported versions (9.2, 10.1, 10.2).
Regarding the issue where the event is not being fired for all dynamically generated columns - could you please provide more information what exactly this means?
Does it men that you are creating columns at runtime when the Grid has already been bound to the data source, or it just means that the columns were not automatically generated (AutogenerateColumns=False)?
Thanks in advance,
I am seeing this same issue in version 10.1.20101.2022 of the XamWebGrid. We have recently upgraded and have noticed that the CellControlAttached event is no longer getting fired for any of the dynamically created columns on our grid.
Myles
I updated to version 9.2.20092.2062, and now the cell control attached event fires for the cells in the columns that i am created intially on load.
BUT it does not fire when scrolling for these columns, and does for other columns cells.
So i think this bug is still not fixed.
Can you test yourself?