Our application is crashing when adding a condition to a custom filter while recording with Adobe Captivate 5. With Captivate not recording, everything works great. We suspect that Captivate may be using WPF Automation and there may be an issue with conditions in the Custom Filter Selection window.
The event viewer says:Application: DRAMSClient.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Stack:at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])at DRAMSClient.App.Main(System.String[])
We are using the XamDataPresenter 10.3.201003.2116
Our steps to reproduce this is:
We are having a similar problem with Captivate.
Our clinical product is a web application running in IE-8.
The problem child is a .NET 4 thin client. It runs by itself, but crashes each time we attempt to record one interaction. This is a process of adding or altering a medication in a list.
The rows of medications are in a list view. The rows are read-only until the “expanded view” is invoked. This utilizes content control to replace the read-only row content with a grid and panel controls. The interactive grid holds menu and text input controls. The row toggles between these two states.
The program crashes on invocation of the expanded row while Captivate is running.
The problem emerged when we updated the application to .NET 4. We had been able to record the .NET 3.5 application using Captivate 4, so we tried Cap. 4 on the new build. Same crash.
We are able to record the software with Camtasia.
PS. Say "Hi" to Dan for us. We appreciated his good work while he was helping us.