These constants specify how TestStand responds when encountering two conflicting definitions for the same type. Type conflicts generally occur when TestStand reads a type from a sequence file that has a different structure than the type already loaded in TestStand.
- ConflictHandler_Error–(Value: 1) Specifies that the method should return an error if there are type conflicts.
- ConflictHandler_Prompt–(Value: 3) Specifies that the method should prompt the user with a dialog box to resolve each type conflict.
- ConflictHandler_UseGlobalType–(Value: 4) Specifies that the method should convert the conflicting type to the currently loaded (global) type if there is a type conflict.
See Also
Engine.GetSequenceFileEx
Engine.UnserializeObjects
PropertyObject.ReadEx
PropertyObject.UnserializeEx
PropertyObjectFile.HandleTypeConflicts
PropertyObjectFile.ReadFile