A Full-Screen Slide in Mid-Game - Revision history

Geep: Change category tag to {{GUI}}, that includes Editing

2022-11-04T18:06:51Z

Change category tag to {{GUI}}, that includes Editing

← Older revision		Revision as of 18:06, 4 November 2022
Line 185:		Line 185:
	[[Full-Screen Video Cutscenes]] has more about deploying "skippable" video cutscenes.		[[Full-Screen Video Cutscenes]] has more about deploying "skippable" video cutscenes.

	{{~~editing~~}}		{{GUI\|sort=Full-Screen Slide}}
	[[Category:Video and cutscenes]]		[[Category:Video and cutscenes]]
	[[Category:Scripting]]		[[Category:Scripting]]
	[[Category:Fonts]]		[[Category:Fonts]]

Geep: /* An Actual Example */ typo

2022-11-04T00:12:16Z

An Actual Example: typo

← Older revision		Revision as of 00:12, 4 November 2022
Line 126:		Line 126:
	[[File:Away0 if skip first cutscene.jpg\|thumb\|center\|A more-complex example of an actual slide. Click to expand.]]		[[File:Away0 if skip first cutscene.jpg\|thumb\|center\|A more-complex example of an actual slide. Click to expand.]]

	The "Continue" text provides a mental target for the cursor, but the gamer can really click anywhere. The custom .gui in this case uses multiple windowDefs with ~~differnt~~ margins, font colors, and font sizes to position text blocks atop the scroll.		The "Continue" text provides a mental target for the cursor, but the gamer can really click anywhere. The custom .gui in this case uses multiple windowDefs with different margins, font colors, and font sizes to position text blocks atop the scroll.

	windowDef CutSceneReplacementSlide		windowDef CutSceneReplacementSlide

Demagogue: /* For More */

2021-11-27T00:52:21Z

For More

← Older revision		Revision as of 00:52, 27 November 2021
Line 177:		Line 177:

	==For More==		==For More==
	The information here draws on 2004-vintage GUI tutorials by Doom creator John ~~Cormac~~, but adapted to TDM and the context here.		The information here draws on 2004-vintage GUI tutorials by Doom creator John Carmack, but adapted to TDM and the context here.

	[[Mission Title Screen while Loading]] has more about the Doom3 GUI layout language with further examples.		[[Mission Title Screen while Loading]] has more about the Doom3 GUI layout language with further examples.

Geep: /* For More */ Link to Mission Title article; comment about editGUIs

2021-11-26T17:06:33Z

For More: Link to Mission Title article; comment about editGUIs

← Older revision		Revision as of 17:06, 26 November 2021
Line 178:		Line 178:
	==For More==		==For More==
	The information here draws on 2004-vintage GUI tutorials by Doom creator John Cormac, but adapted to TDM and the context here.		The information here draws on 2004-vintage GUI tutorials by Doom creator John Cormac, but adapted to TDM and the context here.

			[[Mission Title Screen while Loading]] has more about the Doom3 GUI layout language with further examples.

			You should use a text editor for GUI files. The vintage built-in GUI editor (console command "editGUIs") has become unusable.

	[[Full-Screen Video Cutscenes]] has more about deploying "skippable" video cutscenes.		[[Full-Screen Video Cutscenes]] has more about deploying "skippable" video cutscenes.

Geep: /* Case 1 – Transparent Background, White Letters */

2021-11-26T02:58:59Z

Case 1 – Transparent Background, White Letters

← Older revision		Revision as of 02:58, 26 November 2021
Line 32:		Line 32:
	The text will be word-wrapped and left-justified. You can add "textalign 1" to center it (Sometimes with "textalign 1", the first line stays left-justified; ugh. If so, stick in some leading spaces).		The text will be word-wrapped and left-justified. You can add "textalign 1" to center it (Sometimes with "textalign 1", the first line stays left-justified; ugh. If so, stick in some leading spaces).

	This is not very different than the standard atdm:gui_message treatment with the "...no_art" gui. However, if you want to have titles and paragraphs with different fonts, sizes, locations, or margins, you can just add additional windowDefs. Another usage would be to tweak the margins to provide a subtitle, instead of full-screen text.		This is not very different than the standard atdm:gui_message treatment with the "...no_art" gui. However, if you want to have titles and paragraphs with different fonts, sizes, locations, or margins, you can just add additional windowDefs. More about that below. Another usage would be to tweak the margins to provide a subtitle, instead of full-screen text.

	==Case 2 – Opaque Black Background, White Letters==		==Case 2 – Opaque Black Background, White Letters==

Geep: /For More/ Add templates, link

2021-11-26T02:53:58Z

For More: Add templates, link

← Older revision		Revision as of 02:53, 26 November 2021
Line 174:		Line 174:
	}		}

	The corresponding script function (in emily_related.script) is far more complicated than what was discussed earlier, because it handles ~~many~~ FM-specific chores.		The corresponding script function (in emily_related.script) is far more complicated than what was discussed earlier, because it handles the video, sound, and additional FM-specific chores for story continuity.

	==For More==		==For More==
	The information here draws on 2004-vintage GUI tutorials by Doom creator John Cormac, but adapted to TDM and the context here.		The information here draws on 2004-vintage GUI tutorials by Doom creator John Cormac, but adapted to TDM and the context here.

			[[Full-Screen Video Cutscenes]] has more about deploying "skippable" video cutscenes.

			{{editing}}
			[[Category:Video and cutscenes]]
			[[Category:Scripting]]
			[[Category:Fonts]]

Geep: /* Case 4 – Two-Level Image Background, Black Letters */

2021-11-26T02:08:05Z

Case 4 – Two-Level Image Background, Black Letters

← Older revision		Revision as of 02:08, 26 November 2021
Line 102:		Line 102:

	==Case 4 – Two-Level Image Background, Black Letters==		==Case 4 – Two-Level Image Background, Black Letters==
	There are a number of pre-existing TDM "parchment" and "scroll" backgrounds that have wide transparent perimeters. You ~~can~~ substitute one of these directly (so you see the game world around the edges~~), or create a child windowDef with one of these~~, ~~atop a parent’s~~ opaque background (~~black~~ in ~~this example~~):		There are a number of pre-existing TDM "parchment" and "scroll" backgrounds that have wide transparent perimeters. You could substitute one of these directly, in the style of Case 3, so you see the game world around the edges. Instead, we use "backcolor" to set an opaque black background (as in Case 2), and define the scroll atop it within a child windowDef:

	windowDef MySlide		windowDef MySlide

Geep: /* An Actual Example */

2021-11-26T01:59:55Z

An Actual Example

← Older revision		Revision as of 01:59, 26 November 2021
Line 143:		Line 143:
	}		}
	windowDef Text1 {		windowDef Text1 {
	rect 10, 30, 620, 460 // x, y, w, h. Margins enlarged to keep text on opaque portion of Scroll1		rect 10, 30, 620, 460 // x, y, w, h. Margins enlarged to keep text on opaque upper portion of Scroll1
	text "What Emily Will Say in Her Diary"		text "What Emily Will Say in Her Diary"
	forecolor 1, 1, 1, 1 // White opaque font		forecolor 1, 1, 1, 1 // White opaque font
Line 151:		Line 151:
	}		}
	windowDef Text2 {		windowDef Text2 {
	rect 100, 70, 440, 250 // x, y, w, h. Margins enlarged to keep text on opaque portion of Scroll1		rect 100, 70, 440, 250 // x, y, w, h. Margins enlarged to keep text on opaque middle portion of Scroll1
	text "I startled from my prayers. There he was in my room, & he brought what we need! I snatched the key from him & flung open the long-locked door, the night air so sweet. My passion arose, and he responded ."		text "I startled from my prayers. There he was in my room, & he brought what we need! I snatched the key from him & flung open the long-locked door, the night air so sweet. My passion arose, and he responded ."
	forecolor 0, 0, 0, 1 // Black opaque font		forecolor 0, 0, 0, 1 // Black opaque font
Line 158:		Line 158:
	}		}
	windowDef Text3 {		windowDef Text3 {
	rect 100, 280, 440, 250 // x, y, w, h. Margins enlarged to keep text on opaque portion of Scroll1		rect 100, 280, 440, 250 // x, y, w, h. Margins enlarged to keep text on opaque middle portion of Scroll1
	text "But horrors! I heard Bleda's gait, his footsteps approach. He would kill us! I bolted out the door, shouting ' Follow Me'!"		text "But horrors! I heard Bleda's gait, his footsteps approach. He would kill us! I bolted out the door, shouting ' Follow Me'!"
	forecolor 0, 0, 0, 1 // Black opaque font		forecolor 0, 0, 0, 1 // Black opaque font
Line 165:		Line 165:
	}		}
	windowDef Text4 {		windowDef Text4 {
	rect 10, 420, 590, 40 // x, y, w, h. Margins enlarged to keep text on opaque portion of Scroll1		rect 10, 420, 590, 40 // x, y, w, h. Margins enlarged to keep text on opaque lower portion of Scroll1
	text "Continue"		text "Continue"
	forecolor 1, 1, 1, 1 // White opaque font		forecolor 1, 1, 1, 1 // White opaque font
	textscale 0.5		textscale 0.5
	textalign 1		textalign 1 // Centered
	font "fonts/carleton"		font "fonts/carleton"
	}		}

Geep: /* Overview */

2021-11-26T01:55:10Z

Overview

← Older revision		Revision as of 01:55, 26 November 2021
Line 3:		Line 3:
	Suppose you want to briefly show some text on-screen, but the existing TDM message gui’s don’t quite do what you want. Here’s how you can easily modify them.		Suppose you want to briefly show some text on-screen, but the existing TDM message gui’s don’t quite do what you want. Here’s how you can easily modify them.

	Start by creating an atdm:gui_message entity in your map. Then, in the Entity Inspector, alter these 2 lines to:		Start by creating an atdm:gui_message entity in your map. Then, in the Entity Inspector, rename it to atdm_gui_message_slide, and alter these 2 lines to:
	gui guis/my_slide.gui		gui guis/my_slide.gui
	show <number of seconds you want slide to appear>		show <number of seconds you want slide to appear>

Geep: /* Overview */

2021-11-26T01:49:52Z

Overview

← Older revision		Revision as of 01:49, 26 November 2021
Line 9:		Line 9:

	Arrange for your player to trigger this entity. Finally, we will create and customize my_slide.gui. In particular, we will make it possible for the user to terminate the slide early, by clicking the LMB on it. The text we will display will be hardcoded into the .gui, not passed as a spawnarg or (as would be the case with readables) retrieved from an .xd file.		Arrange for your player to trigger this entity. Finally, we will create and customize my_slide.gui. In particular, we will make it possible for the user to terminate the slide early, by clicking the LMB on it. The text we will display will be hardcoded into the .gui, not passed as a spawnarg or (as would be the case with readables) retrieved from an .xd file.

			The Doom GUI language is not a thing of beauty. Some places require semi-colons at line ends; some places forbid them. Sometimes you need quotes; sometimes not. Persevere.

	==Case 1 – Transparent Background, White Letters==		==Case 1 – Transparent Background, White Letters==

A Full-Screen Slide in Mid-Game - Revision history

Geep: Change category tag to {{GUI}}, that includes Editing

Geep: /* An Actual Example */ typo

Demagogue: /* For More */

Geep: /* For More */ Link to Mission Title article; comment about editGUIs

Geep: /* Case 1 – Transparent Background, White Letters */

Geep: /*For More*/ Add templates, link

Geep: /* Case 4 – Two-Level Image Background, Black Letters */

Geep: /* An Actual Example */

Geep: /* Overview */

Geep: /* Overview */

Geep: /For More/ Add templates, link