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. Image for the cookie policy date

Hide row

After having downloaded the new version, the following piece of code (nested in much larger class) will freeze the application and eat up 100 pct of the CPU. If the if-statement is true, everything hangs on setting the first row to true: if( !this.Rows.Hidden[1] ) this.Rows.Hidden[1] = true; I have not been able to reproduce this with a simple demo, but the problem only exist if we use the new version of the grid (1.6.1) not the old version (1.5.2). Do you have any ideas as to what we might be doing elsewhere that affects the Hidden-property? Any postings would be greatly appriciated, since I have no clue what we are doing wrong. Sincerly Soren

1 Reply

AD Administrator Syncfusion Team June 26, 2003 11:17 AM

If you have the source code version you could enable tracing. Just copy/modify the gridpad.exe.config into your apps folder with the exe and then rename it to yourapp.exe.config. Another idea would be to do "Debug|Break All" and check out the call stack. Does it always at the same method. Take also a close look at any events you are handling. Maybe some of your events cause a infinite recursion and you could break that cycle by haveing some kind of boolean flag to avoid reentry into that method. Stefan

Loader.
Live Chat Icon For mobile
Up arrow icon