Reusing Scenario Components - Revision history

Anna Dizack: Anna Dizack moved page Introduction II to Reusing Scenario Components: Name

2017-02-24T21:46:16Z

Anna Dizack moved page Introduction II to Reusing Scenario Components: Name

Anna Dizack at 21:44, 24 February 2017

2017-02-24T21:44:01Z

Ciera Headley at 01:04, 7 December 2016

2016-12-07T01:04:36Z

Ciera Headley at 00:52, 7 December 2016

2016-12-07T00:52:36Z

Ciera Headley at 23:47, 5 December 2016

2016-12-05T23:47:00Z

Ciera Headley at 23:45, 5 December 2016

2016-12-05T23:45:39Z

Show changes

Ciera Headley: Created page with "==Introduction== Reuse is a desirable characteristic of any system that involves the development of detailed and laborious specifications. The ISAT allows the specification o..."

2016-12-05T23:43:36Z

Created page with "==Introduction== Reuse is a desirable characteristic of any system that involves the development of detailed and laborious specifications. The ISAT allows the specification o..."

Show changes

← Older revision		Revision as of 21:44, 24 February 2017
Line 1:		Line 1:
		+	[[ISAT_User%27s_Guide_Table_of_Contents\|ISAT User's Guide Table of Contents]]
		+
	[[Visual_Trigger_Representation\|◄PREVIOUS]] [[Reuse_through_Groups\|NEXT►]]		[[Visual_Trigger_Representation\|◄PREVIOUS]] [[Reuse_through_Groups\|NEXT►]]
	==Introduction==		==Introduction==

← Older revision		Revision as of 01:04, 7 December 2016
Line 39:		Line 39:

	[[#top\|TOP]]		[[#top\|TOP]]
		+
		+	[[Visual_Trigger_Representation\|◄PREVIOUS]] [[Reuse_through_Groups\|NEXT►]]

@@ Line 8: / Line 8: @@
 Because the solution of these problems is an active area of research, the ISAT utilizes two simpler methods to allow reuse. The first involves the use of Copy and Paste operations to reuse single scenario elements, and the second uses a Component Merge capability for reusing additional components.
 ==Reuse through Copy and Paste==
@@ Line 14: / Line 15: @@
 This approach becomes problematic, however, in cases when many individual scenario elements have to be copied (as in the case of having manually placed numerous static objects all over the map), or for high-level coordinators such as the TM or TLM that cannot be copied to the clipboard. For such cases, use of the Component Merge capability can provide a solution.
 == Reuse through Component Merge==
@@ Line 35: / Line 37: @@
 In addition to global components, the Component Merge dialog box gives a list of individual traffic elements in the new file. Selecting any of them will copy them to the current file using their exact same placement and properties.

← Older revision		Revision as of 23:47, 5 December 2016
Line 1:		Line 1:
−	[[~~Introduction_II~~\|◄PREVIOUS]] [[Reuse_through_Groups\|NEXT►]]	+	[[Visual_Trigger_Representation\|◄PREVIOUS]] [[Reuse_through_Groups\|NEXT►]]
	==Introduction==		==Introduction==

← Older revision	Revision as of 21:46, 24 February 2017
(No difference)