Display Creator - Revision history

BenR at 14:29, 27 October 2025

2025-10-27T14:29:48Z

BenR: /* Touchable items */

2025-10-27T14:25:51Z

Touchable items

BenR at 14:17, 27 October 2025

2025-10-27T14:17:48Z

BenR at 14:16, 27 October 2025

2025-10-27T14:16:08Z

BenR at 14:11, 27 October 2025

2025-10-27T14:11:46Z

BenR at 14:00, 27 October 2025

2025-10-27T14:00:45Z

BenR at 13:55, 27 October 2025

2025-10-27T13:55:18Z

BenR at 13:51, 27 October 2025

2025-10-27T13:51:26Z

BenR at 13:49, 27 October 2025

2025-10-27T13:49:50Z

BenR: /* A typical program */

2025-10-27T13:44:45Z

A typical program

← Older revision		Revision as of 14:29, 27 October 2025
Line 67:		Line 67:
	Without callback you will need to manually compare the touchID returned by the CheckForTouch component macro. It is possible that the same ID is used by different items on different scenes so you will need to keep track of the current scene using a variable.		Without callback you will need to manually compare the touchID returned by the CheckForTouch component macro. It is possible that the same ID is used by different items on different scenes so you will need to keep track of the current scene using a variable.

		+	[[File:WYSIWYG_7.png\|Checking for touch IDs]]


		+	===With Callback===

		+	With callback enabled you instead define a callback macro in the touchble primitive properties which will be called when the item it touched as part of the CheckForTouch component macro.

−	~~===With~~ Callback~~===~~	+	The callback macro has a parameter of type handle which contains the unique handle of the item touched and can be compared like this.
		+
		+	[[File:WYSIWYG_8.png\|Callback macro]]

← Older revision		Revision as of 14:25, 27 October 2025
Line 64:		Line 64:

	===Without Callback===		===Without Callback===
		+
		+	Without callback you will need to manually compare the touchID returned by the CheckForTouch component macro. It is possible that the same ID is used by different items on different scenes so you will need to keep track of the current scene using a variable.
		+
		+



	===With Callback===		===With Callback===

← Older revision		Revision as of 14:17, 27 October 2025
Line 60:		Line 60:

	Each Display Creator panel will automatically take the background colour defined in the Display Manager component but this background colour can be overridden by altering the Display Background Colour property available when clicking on a blank area of the Display Creator Panel.		Each Display Creator panel will automatically take the background colour defined in the Display Manager component but this background colour can be overridden by altering the Display Background Colour property available when clicking on a blank area of the Display Creator Panel.
		+
		+	==Touchable items==
		+
		+	===Without Callback===
		+
		+
		+
		+	===With Callback===

@@ Line 7: / Line 7: @@
 A way to solve this problem is to allow the layout of the display to be defined graphically.
-The display manager component is capable of managing special scene component panels which can be used as placeholders that can show the layout of the screen and allow you to graphically create and control a design.
+The display manager component is capable of managing special Display Creator panels which can be used as placeholders that can show the layout of the screen and allow you to graphically create and control a design.
@@ Line 14: / Line 14: @@
 To begin simply add your selected GLCD component to the 2d panel and then add a display manager component.
-The display manager component will automatically link to the GLCD and automatically create a single layout scene which will appear after a few seconds.
+The display manager component will automatically link to the GLCD and automatically create a single Display Creator panel which will appear after a few seconds.
-The display manager component has additional properties to allow you to add more scenes and define which scenes are used by the component. Increasing the number of scenes e.g. from 1 to 4 will automatically add more layout scenes to your project after a few seconds.
+The display manager component has additional properties to allow you to add more Display Creator panels (scenes) and define which Display Creator panels are used by the component. Increasing the number of scenes e.g. from 1 to 4 will automatically add more Display Creator panels to your project after a few seconds.
 [[File:WYSIWYG_1.png|Component and Layout scene panels]]
@@ Line 29: / Line 29: @@
 ==A typical bare bones program==
-Here is a very basic program to initialise the GLCD, the Display manager and then display the contents of the first layout scene panel.
+Here is a very basic program to initialise the GLCD, the Display manager and then display the contents of the first Display Creator panel.
 [[File:WYSIWYG_3.png|Component and Layout scene panels]]
@@ Line 45: / Line 45: @@
-==Using the layout panels==
+==Using the Display Creator layout panels==
-The layout scene panels control what will be shown on each scene of the GLCD. You might for example want a main screen, a menu screen and then a config screen.
+The Display Creator panels control what will be shown on each scene of the GLCD. You might for example want a main screen, a menu screen and then a config screen.
 The Scene panels can be renamed to better identify their role in the program. To do this use the Panels tab of the Project Explorer, right click the scene you want to rename and select Rename.
@@ Line 53: / Line 53: @@
 [[File:WYSIWYG_5.png|Renaming scene panel]]
-The Display Manager component allows you to select which Scene panel will be referenced for each numeric Scene you want to display.
+The Display Manager component allows you to select which Display Creator panel will be referenced for each numeric Scene you want to display.
-The Graphical Manager Primitives can be added to each Scene panel and you can do things like move, scale, copy, paste, align etc with these primitives like you can on a normal component panel. The Snap to grid feature can also be useful to easily acheiving uniform scaling and spacing between primitives.
+The Graphical Manager Primitives can be added to each Display Creator panel and you can do things like move, scale, copy, paste, align etc with these primitives like you can on a normal component panel. The Snap to grid feature can also be useful to easily acheiving uniform scaling and spacing between primitives.
 [[File:WYSIWYG_6.png|Adding Primitives]]

← Older revision		Revision as of 14:11, 27 October 2025
Line 46:		Line 46:

	==Using the layout panels==		==Using the layout panels==
		+
		+	The layout scene panels control what will be shown on each scene of the GLCD. You might for example want a main screen, a menu screen and then a config screen.
		+
		+	The Scene panels can be renamed to better identify their role in the program. To do this use the Panels tab of the Project Explorer, right click the scene you want to rename and select Rename.
		+
		+	[[File:WYSIWYG_5.png\|Renaming scene panel]]
		+
		+	The Display Manager component allows you to select which Scene panel will be referenced for each numeric Scene you want to display.
		+
		+	The Graphical Manager Primitives can be added to each Scene panel and you can do things like move, scale, copy, paste, align etc with these primitives like you can on a normal component panel. The Snap to grid feature can also be useful to easily acheiving uniform scaling and spacing between primitives.
		+
		+	[[File:WYSIWYG_6.png\|Adding Primitives]]

@@ Line 1: / Line 1: @@
 ==What is Display Creator==
-Display creator is a way to graphically control your GLCD scenes using a WYSIWYG type interface.
+Display creator is a way to graphically control your GLCD layout, scenes and user interface (UI) using a what you see if what you get (WYSIWYG) type interface.
-WYSIWYG = What You See Is What You Get
+When creating Graphical Display layouts it can often become more and more complex to manage all the various coordinates, images and primitive shapes and end up with a nice looking display layout.
 A way to solve this problem is to allow the layout of the display to be defined graphically.
-The display manager is capable of managing special scene component panels which can be used as placeholders that can show the layout of the screen and allow you to graphically create a design.
+The display manager component is capable of managing special scene component panels which can be used as placeholders that can show the layout of the screen and allow you to graphically create and control a design.
@@ Line 28: / Line 26: @@
 The Enable Callbacks property allows the touch callback feature on all the Graphical Manager Primitive components, turn this off if you are not using a touch feature or if you want to implement your own touch routines.
 ==A typical program==
 Here is a very basic program to initialise the GLCD, the Display manager and then display the contents of the first layout scene panel.

← Older revision		Revision as of 13:55, 27 October 2025
Line 42:		Line 42:

	{{Fcfile\|DisplayCreator - Touch.fcfx\|DisplayCreator - Touch}}		{{Fcfile\|DisplayCreator - Touch.fcfx\|DisplayCreator - Touch}}
		+
		+	Adding a fixed delay to the loop will allow for reliable touch intervals, for example a loop delay of 10ms and a Touch Repeat Rate of 10 would be 10 x 10ms = 100ms between repeat button presses.


	==Using the layout panels==		==Using the layout panels==

@@ Line 34: / Line 34: @@
 [[File:WYSIWYG_3.png|Component and Layout scene panels]]
+{{Fcfile|DisplayCreator - NoTouch.fcfx|DisplayCreator - NoTouch}}
@@ Line 40: / Line 40: @@
 [[File:WYSIWYG_4.png|Component and Layout scene panels with touch]]
 ==Using the layout panels==

← Older revision		Revision as of 13:49, 27 October 2025
Line 31:		Line 31:

	Here is a very basic program to initialise the GLCD, the Display manager and then display the contents of the first layout scene panel.		Here is a very basic program to initialise the GLCD, the Display manager and then display the contents of the first layout scene panel.
		+
		+	[[File:WYSIWYG_3.png\|Component and Layout scene panels]]
		+
		+
		+
		+
		+	Here is the same program, this time with a touch enabled GLCD. We need to sample the touch sensor and then pass the coordinates to the Display Manager. If there is no touch then we also tell the Display Manager so it can update its touch repeat rate variables.
		+
		+	[[File:WYSIWYG_4.png\|Component and Layout scene panels with touch]]
		+

	==Using the layout panels==		==Using the layout panels==