We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Designer Hangs when adding GridBoundColumns

Thread ID:

Created:

Updated:

Platform:

Replies:

6196 Aug 4,2003 10:15 AM Aug 20,2003 10:17 AM Windows Forms 3
loading
Tags: GridControl
Administrator [Syncfusion]
Asked On August 4, 2003 10:15 AM

I have a databound grid and have already added 4 gridboundcolumns. I test the app - everything is okay. But when go to add a few more, the designer hands - systemidle process goes to 245%!!! Have u jeard this before - any fixes? Charles

Thomas Zueger
Replied On August 5, 2003 12:43 AM

Charles, Sometimes I have the same problem, but it is not reproducable. The only solution is to open a second instance of VS, this will "unlock" the hanging instance. Clay, is this a known problem? Regards, Thomas

Administrator [Syncfusion]
Replied On August 5, 2003 01:23 AM

We have had probably 4 other users report this for VS2003, but to date, have not been able to reproduce it in house. One user, who owned the full product, was able to attach the frozen DevStu process to a 2nd instance of DevStu for debugging, and did a BreakAll. This showed the locked up was in a call to a FrameWork method that was trying to remove sited objects. After about 5 minutes the call returned. He then cleaned his machine, reinstalling .NET 1.1 and VS2003, and the problem went away. We are trying to resolve this problem, but just haven't seen it in-house yet to be able to effectively work on it.

Jeff
Replied On August 20, 2003 10:17 AM

I get this same exact problem and it's killing me! I'm basically forced to code all my grid columns. This is obviously a common problem with VS2003 and the DataGridColumn. The problem typically happens after adding a celltype other than text. > We have had probably 4 other users report this for VS2003, but to date, have not been able to reproduce it in house. One user, who owned the full product, was able to attach the frozen DevStu process to a 2nd instance of DevStu for debugging, and did a BreakAll. This showed the locked up was in a call to a FrameWork method that was trying to remove sited objects. After about 5 minutes the call returned. He then cleaned his machine, reinstalling .NET 1.1 and VS2003, and the problem went away. > > We are trying to resolve this problem, but just haven't seen it in-house yet to be able to effectively work on it. >

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;