I have a really starnge problem. I have a master-detail view where the detail is in a grid.
When I select the first item in the master view, I see three items in the detail view, and when I select the third item in the master view, I see no items in the details view (as it should be). the grid of the details view is long enough to show three rows without scrolling.
When I open the form, the first item is selected. Then I select the third, then again the first and then the third and the first. At this point I should see three items in the details view, but instead I see only the template row and the other rows are hidden above and I see a horizontal scroll bar.
Maybe I could select the first row every time the details view changes, but I didn't find the grid event for that. InitializeRowCollection doesn't fire.
Hi Ken,
I do apologize if you are running into problems. We try pretty hard not to introduce bugs, but occassionally in an environment as complex as DotNet, it does happen.
We certainly want to track down and fix this issue, but in order to do that, we have to be able to see it happen. I'm sure as a developer you understand that you can't fix a problem you can't see. Even if you think you fixed it, how would you know?
I can understand that you are busy and don't have the time to build a new project from scratch to duplicate the issue. One alternative that often works is if you make a copy of your real application and remove things to narrow it down to a small app that your Developer Support folks can use just to see the issue occur. I realize that this is not always possible, of course, depending on how tightly integrated your code is.
Have you reported this issue to Infragistics Developer Support? Perhaps someone else has already reported the issue and they are aware of it. If not, then maybe you could give them some steps to follow so they can try to duplicate the issue without a sample. A sample is usually the easiest way because of the infinite number of variables involved in a DotNet application, but if the problem is common enough, then sometimes they can duplicate the issue just by following your instructions.
Just so you know, these forums are really for peer-to-peer support and this is not the official venue to get assistance from Infragistics Developer Support. I'm just here helping out customers in my spare time. I can offer help on How-to questions and maybe make suggestions, but the Developer Support folks have access to other bug reports and things I don't, so it's a good idea to report this issue to them.
Sidenote: This is the second time in so many days that I am told I need to build an example app to help IG support figure out a bug. I assume most developers don’t have time to mess around debugging IG problems because they have important release dates that need to be hit. CBS spends a pretty penny to purchase your full product line & support. And I keep using other third party controls because the IG controls keep breaking our development every release. Or I keep having to hack around IG bugs. The thought around the shop is that we ditch IG…just to let someone there know.
That clearly should not be the case. Perhaps the issue you are experiencing is not the same one that was fixed. Try duplicating the issue in a small sample project and Submit an incident to Infragistics Developer Support. If they test it out and are still getting the same problem, then either the issue was not fixed properly or this is a new issue that needs to be fixed.
I am using 8.2 of the control build 2022 (the last hotfix) and still have this problem.
The thing is the Hotfix for 8.1 and 8.2 came out at the same time and the fix for this never made it into the 8.2 branch...that just sux!
It's not happening under v8.1 build 2058