Print Page | Close Window

Who's Problem is This?

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1567
Printed Date: 23-Apr-2025 at 5:56pm


Topic: Who's Problem is This?
Posted By: JohnIT
Subject: Who's Problem is This?
Date Posted: 24-Nov-2009 at 7:24am
Ideablade DevForce Classic 3.6.9.1 with Infragistics UltraWinGrid 9.2

Crash on Dispose() of WInGrid when binded with Ideablade only.
Click a cell on the grid, close the form, Crash!

Who's issue is it if Ideablade supports Infragistics 9.2 and the crash only happens when binded with Ideablade?

I need answers, can I fix this somehow or is it a bug that someone else needs to fix?

Thank you.


Replies:
Posted By: JohnIT
Date Posted: 24-Nov-2009 at 12:03pm
Infragistics has said they are looking into it however they would like Ideablade to provide instructions on how to reproduce this error without using Ideablade tools. They said if it is Infragisitcs bug than Ideablade should have no problem reproducing the error without Ideablade tools. Seems like I am in the middle of this. Since they cannot reproduce the error with Ideablade, I am thinking it is an Ideablade bug. Any help would be appreciated, if you can find something I would be happy to forward it along to Infragistics so that this matter can get resolved and I can get back to business.

Posted By: JohnIT
Date Posted: 24-Nov-2009 at 12:04pm
This is a response from Infragistics:

The stack trace doesn't give me any ideas at first glance. We'll pass this on to our developers to see if they have any insight.

The forum links you provided were related to issues that weren't caused by our controls. In the first two (which point to the same thread), our controls weren't even involved in the stack trace. In the third, the issue was caused by incorrect use of threading. None of these scenarios are within our ability to control.

With the information I see, it's not clear whether it's our toolset or Ideablade's that is causing this issue. While our developers take a look at the information that's available, the best next step is for Ideablade to provide us information on how to reproduce this same exception without their tools involved. We don't have Ideablade's toolset to be able to test this ourselves.

Posted By: kimj
Date Posted: 25-Nov-2009 at 2:30pm
We're not yet sure whether this is a DevForce or Infragistics issue either.  We do have a workaround you can try, though.   On those forms where you see the problem, add a FormClosing handler which sets the UltraGrid's DataSource to null.  Here's an example:
 
this.FormClosing += new FormClosingEventHandler(Form1_FormClosing);

void Form1_FormClosing(object sender, FormClosingEventArgs e) {

   this.ultraGrid1.DataSource = null;

}

 

Posted By: michaelparez
Date Posted: 08-Jan-2010 at 2:26am
Hi John  IT,
I didn't understand what your talking about ,can you give me a clear idea about what your speaking?


-------------
%20http://www.master-fix.com/london/decorating.html - east london carpenter

Posted By: davidklitzke
Date Posted: 08-Jan-2010 at 7:45am
The problem occurs only on some solutions depending upon the particular sequencing of events.  We at IdeaBlade Technical Support had a hard time reproducing the problem at first.  If you don't see the symptom (i.e., Dispose() of WInGrid when binded with Ideablade only. Click a cell on the grid, close the form, Crash! ), I would not worry about it.


Print Page | Close Window