Addition of new row crashes the app...

590

CuriousCat posted over 16 years ago

I have xamDataGrid that binds to a dataset.

I have

<igDP:XamDataGrid.FieldLayoutSettings>

<igDP:FieldLayoutSettings AddNewRecordLocation="OnTopFixed" AllowAddNew="True"/>

</igDP:XamDataGrid.FieldLayoutSettings>

so I can edit the grid. Grid loads fine and displays everything in the dataset fine. I have a row at the top to enter new data into the grid.

After I am done adding the new row, I hit enter to add the row to the grid and that crashes.

I then tried your sample that I have, crashes in the same way. Is there a fix for this, hot fix or something that I should get?

I really need this fix ASAP. I greatly appreciate your help.

Thanks.

590

CuriousCat posted over 16 years ago in reply to Joe Modica

Joe,

Thank you so much for all that info. I am happy to hear that there will be hotfix released soon to address these issues.

I appreciate your quick responses.
Cancel
Reply

Cancel
8576

Offline Joe Modica posted over 16 years ago in reply to CuriousCat

Hi -

I am glad to hear that it is working OK for you now.

As for the checkbox issue - unfortunately this is a regression that we introduced in the 7.2 version. There will be a 7.2 hotfix release available within the next couple of days that fixes this regression and some other issues. I apologize for the inconvenience.

Joe
Cancel
Reply

Cancel
8576

Offline Joe Modica posted over 16 years ago in reply to CuriousCat

Hi -

This was definitely fixed in the 7.2 release. The exception is actually caused by a bug in the WPF ItemsControl that was introduced in the .NET 3.5 framework. The FatalExecutionEngineError (which is not trappable via try/catch) is being generated by the WPF ItemsControl when it is bound to an IBindingList data source on which AddNew is called (in fact you can duplicate this with a standard WPF ItemsControl that is bound to an IBindingList by call AddNew on the IBindingList interface).

The reason the bug surfaced in the XamDataGrid is that we were using an ItemsControl internally in the 7.1 version. We removed removed the ItemsControl in the 7.2 version (there will be a hotfix for 7.1 users available this week that includes this change).

I don't know why you are still seeing this error if you are using the 7.2 release. Is it possible that you have an ItemsControl in your application that is bound to the same DataSource as the XamDataGrid?

Joe
Cancel
Reply

Cancel
590

CuriousCat posted over 16 years ago in reply to CuriousCat

I downloaded the latest dlls and I dont see the problem anymore. That is fixed however I have another problem that this download created that I didn't have before.

Download broke my grid's functionality.

I have a bool in my dataset and it used to display the right data in the grid prior to this download and now the check box has a green square in it instead of the check mark or empty checkbox depending on the data in the dataset for the field.

I have these in my references,

Infragistics3.WPF.DataPresenter.v7.2

Infragistics3.WPF.Editors.v7.2

Infragistics3.WPF.v7.2

Am I missing a reference that might have possible broke my grid or is it a problem in this version?

Thans a bunch.
Cancel
Reply

Cancel
590

CuriousCat posted over 16 years ago in reply to Joe Modica

Here is the message from the exception

FatalExecutionEngineError was detected
Message: The runtime has encountered a fatal error.
The address of the error was at 0x56d7b7a7, on thread 0xf34.
The error code is 0x80131623.
This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code.
Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

Also, refer to this thread that someone else posted and you guys said it's been fixed but still happens to me with my app and your browser sample, I am not sure what I am missing..... I am using V7.2

http://forums.infragistics.com/forums/t/2018.aspx

I will try to create a small sample to send you sometime this evening......I badly need a fix for this
Cancel
Reply

Cancel