Hi,
I am using Infragistics UltraWinGrid v7.3, and I have a few concerns:
1)-
My Initialize Row event, sometimes , does not fire on a cell/row update, thereby missing a few row/cell coloring tasks. Eg: this is what im telling it to do ->
if Column 'Y' ==1 , color the row blue, else use default color.
if Column 'X' == 2, color cell at column 'Z' red,
else if X == 1 color 'Z' cell green, else use default color.
Ever so often , I have Y==1, and the row is still in the default color ... but if some other row value changes (like X==1) , then Z cell becomes green and the row becomes blue. This occurs rarely, but noticably ... so what I do is force these coloring checks upon each datasource update => this makes the grid behave like it should.
Do you know why this happens, and any workaround for this?
2)
Another oddity I noticed occurs very rarely, but is of great concern. Sometimes my grid renders the same row multiple times, one below the other ... to make matters worse, any update on the original row, updates these 'copies' as well. The only way to get rid of this is to restart my grid.
This 'duplication' also varies, once I noticed the same row appearing 4 times ... recently I noticed on row appearing 11 times. I have noticed this about 4-5 other times in the past 6 months.
Do you have any solution for this?
Thanks.
Both of these issues sounds like old bugs that were fixed years ago.
Make sure you have the latest service release: How to get the latest service release - Infragistics Community
Thanks Mike.
Since the software is licenced to my firm, I cant seem to get this information. Is this a service release for the specific version (UltraWinGrid 7.3)?
Also Where can I find known bugs and issues with this particular version, and the fixes for them? Thanks.
Yes, there is a service release for NetAdvantage 7.3.
And I am pretty sure there is a list of what is fixed in the service release on the same page with the service release itself.
I am now using NetAdvantage v8.1, and while I do not see the row repeating problem, The initialize Row bug doesn't appear to be fixed. Whenever a lot of Data Updates occur, some of the changes fail to fire the initialize row event ... because of this I am forced to do the row initialization within the row update event, which is unnecessary and unsafe.Do you know what could be causing this? Thanks.
I was not suggesting that you update to a new version of NetAdvantage, only that you get the latest service release for whatever version you are using.
So... are you using the latest service release for NetAdvatange v8.1?
There's not much we can do to fix a problem we cannot reproduce. I am certainly not suggesting that you send us your real application - that would be far to large for us to debug, anyway.
What we really need here is a small sample project with as little as possible to just demonstrate the issue.
There are two ways you could go about attempting to create a sample. One is to start a new project and build up until you get the problem to occur. The other is to start with your actual project and then remove things until you reduce it down to something managable.
Personally, I prefer the second options. You can copy your existing project and then remove pieces of it until you either narrow down the code that causes it or end up with a sample you can send us.
Today I noticed the row repeating problem again, where one row is repeated multiple times.
I can get around the initialize row not firing by performing those functions in the update row function (even though it is not safe to do so), but I don't have a workaround for this. What do you suggest I do? I'm all out of ideas.
I could send you an edited screenshot if you want, but a sample project would not be possible since the application is proprietary.
That appears to be the latest. So if InitializeRow is still not firing, we would need to see a small sample project demonstrating this behavior so we can check it out.
I installed the latest service release , and it seemed to be a lot better at firing the initialize row event, but I noticed quite a few missed updates ... so it seems like the bug wasn't fixed in this coz the event was still not being fired at certain times
This is the Service Release I used NetAdvantage_WinForms_20081_CLR20_SR_2161.msp
Is this the correct one? If yes, then when can i expect a fix for this? if not then which one should i use. The admin team provides me with these utilities, so It'll be really helpful if you can give me the name of the exact service release.
It depends when the bug was fixed. If it was fixed before the release of v8.1, then the fix would be in there. But if it was fixed after that, then it would not have been available until the service release. :)