Multiple displays - Revision history

Tectu: /* Access the displays */

2016-05-19T17:19:22Z

‎Access the displays

Tectu at 00:39, 14 February 2015

2015-02-14T00:39:10Z

Tectu at 00:38, 14 February 2015

2015-02-14T00:38:43Z

Inmarket: /* Access the displays */

2014-08-16T04:33:57Z

‎Access the displays

Tectu at 00:14, 3 July 2014

2014-07-03T00:14:26Z

Tectu at 00:09, 3 July 2014

2014-07-03T00:09:08Z

Tectu: /* Configuration */

2014-07-03T00:06:27Z

‎Configuration

Tectu at 00:06, 3 July 2014

2014-07-03T00:06:16Z

Tectu: /* Access the displays */

2014-07-03T00:05:50Z

‎Access the displays

Tectu at 00:05, 3 July 2014

2014-07-03T00:05:11Z

@@ Line 101: / Line 101: @@
      /* Initialize and clear the display */
-     gfxInit();;
+     gfxInit();
      /* Cycle through each display */

← Older revision		Revision as of 00:39, 14 February 2015
Line 2:		Line 2:
	A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays\|remote display]] support.		A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays\|remote display]] support.

−	~~This article is related to [[Pixmaps\|Pixmaps]] as they use the same API.~~

	== Configuration ==		== Configuration ==

@@ Line 1: / Line 1: @@
 It's possible to drive more than just one display out of the [[GDISP]] module. Each display is completely independent. The displays can have different display controllers and therefore different interfaces and also different resolutions. Note: "multiple displays" means that you can also use more than just two displays.
 A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays|remote display]] support.
 == Configuration ==
@@ Line 127: / Line 129: @@
+}
 </syntaxhighlight>
 [[Category:GDISP]]

@@ Line 60: / Line 60: @@
 int main(void) {
-	coord_t		width, height;
+    coord_t    width, height;
-	coord_t		display, i, j;
+    coord_t    display, i, j;
-	/* Initialize and clear the display */
+    /* Initialize and clear the display */
-	gfxInit();
+    gfxInit();
-	/* Cycle through each display */
+    /* Cycle through each display */
-	for(display = 0; display < GDISP_TOTAL_DISPLAYS; display++) {
+    for(display = 0; display < GDISP_TOTAL_DISPLAYS; display++) {
-	/* Set the default display to the specified display */
+        /* Set the default display to the specified display */
-	gdispSetDisplay(gdispGetDisplay(display));
+        gdispSetDisplay(gdispGetDisplay(display));
-	/* Get the screen size */
+        /* Get the screen size */
-	width = gdispGetWidth();
+        width = gdispGetWidth();
-	height = gdispGetHeight();
+        height = gdispGetHeight();
-	/* Draw draw draw */
+        /* Draw draw draw */
-	gdispDrawBox(10, 10, width/2, height/2, Yellow);
+        gdispDrawBox(10, 10, width/2, height/2, Yellow);
-	gdispDrawLine(5, 30, width-50, height-40, Red);
+        gdispDrawLine(5, 30, width-50, height-40, Red);
-	for(i = 5, j = 0; i < width && j < height; i += 7, j += i/20)
+        for(i = 5, j = 0; i < width && j < height; i += 7, j += i/20)
-		gdispDrawPixel(i, j, White);
+            gdispDrawPixel(i, j, White);
-−
+    }
-	while(TRUE) {
+    while(TRUE) {
-		gfxSleepMilliseconds(500);
+        gfxSleepMilliseconds(500);
-−
+    }
+}
 </syntaxhighlight>
@@ Line 95: / Line 95: @@
 int main(void) {
-	coord_t		width, height;
+    coord_t    width, height;
-	coord_t		display, i, j;
+    coord_t    display, i, j;
-	GDisplay	*g;
+    GDisplay   *g;
-	/* Initialize and clear the display */
+    /* Initialize and clear the display */
-	gfxInit();;
+    gfxInit();;
-	/* Cycle through each display */
+    /* Cycle through each display */
-	for(display = 0; display < GDISP_TOTAL_DISPLAYS; display++) {
+    for(display = 0; display < GDISP_TOTAL_DISPLAYS; display++) {
-	/* Get the specified display */
+        /* Get the specified display */
-	g = gdispGetDisplay(display);
+        g = gdispGetDisplay(display);
-	/* Get the screen size */
+        /* Get the screen size */
-	width = gdispGGetWidth(g);
+        width = gdispGGetWidth(g);
-	height = gdispGGetHeight(g);
+        height = gdispGGetHeight(g);
-	/* Draw draw draw */
+        /* Draw draw draw */
-	gdispGDrawBox(g, 10, 10, width/2, height/2, Yellow);
+        gdispGDrawBox(g, 10, 10, width/2, height/2, Yellow);
-	sprintf(buf, "Display %u", display);
+        sprintf(buf, "Display %u", display);
-	gdispGFillStringBox(g, width/2, height/2, width/2-10, height/2-10, buf, f, White, Blue, justifyCenter);
+        gdispGFillStringBox(g, width/2, height/2, width/2-10, height/2-10, buf, f, White, Blue, justifyCenter);
-	gdispGDrawLine(g, 5, 30, width-50, height-40, Red);
+        gdispGDrawLine(g, 5, 30, width-50, height-40, Red);
-	for(i = 5, j = 0; i < width && j < height; i += 7, j += i/20)
+        for(i = 5, j = 0; i < width && j < height; i += 7, j += i/20)
-		gdispGDrawPixel(g, i, j, White);
+            gdispGDrawPixel(g, i, j, White);
-−
+    }
-	while(TRUE) {
+    while(TRUE) {
-		gfxSleepMilliseconds(500);
+        gfxSleepMilliseconds(500);
-−
+    }
+}
 </syntaxhighlight>

← Older revision		Revision as of 00:14, 3 July 2014
Line 1:		Line 1:
−	It's possible to drive more than just one display out of the GDISP module. Each display is completely independent. The displays can have different display controllers and therefore different interfaces and also different resolutions. Note: "multiple displays" means that you can also use more than just two displays.	+	It's possible to drive more than just one display out of the [[GDISP]] module. Each display is completely independent. The displays can have different display controllers and therefore different interfaces and also different resolutions. Note: "multiple displays" means that you can also use more than just two displays.
	A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays\|remote display]] support.		A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays\|remote display]] support.

@@ Line 1: / Line 1: @@
 It's possible to drive more than just one display out of the GDISP module. Each display is completely independent. The displays can have different display controllers and therefore different interfaces and also different resolutions. Note: "multiple displays" means that you can also use more than just two displays.
-A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[remote display]] support.
+A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[Remote displays|remote display]] support.
 == Configuration ==
@@ Line 130: / Line 130: @@
 == Limitations ==
 As this is more a work-in-progress feature, it is currently '''NOT''' possible to have more than one input touch device (through the [[GINPUT#Touchscreen|GINPUT touch]] module).

@@ Line 32: / Line 32: @@
 </syntaxhighlight>
 From now on, you can access all your displays independently.
 == Example - Different controllers ==

← Older revision		Revision as of 00:06, 3 July 2014
Line 2:		Line 2:
	A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[remote display]] support.		A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[remote display]] support.

		+	== Configuration ==
	When dealing with multiple displays, GFX distinguishes between the displays and the controller types. This is useful for when using the same type of display controller more than once so you don't have to include the code multiple times.		When dealing with multiple displays, GFX distinguishes between the displays and the controller types. This is useful for when using the same type of display controller more than once so you don't have to include the code multiple times.

@@ Line 54: / Line 54: @@
 == Access the displays ==
-Your displays are now set up and you can access them. There are two different ways to do so. One way is to select the current active display through the <code>gdispSetDisplay()</code> call and use the <code>gdispXxx()</code> routines as you would with just one display. The other way is to use the <code>dispGXxx()</code> call instead where the first parameter is always the display that shall be accessed.
+Your displays are now set up and you can access them. There are two different ways to do so. One way is to select the current active display through the <code>gdispSetDisplay()</code> call and use the <code>gdispXxx()</code> routines as you would with just one display. The other way is to use the <code>gdispGXxx()</code> call instead where the first parameter is always the display that shall be accessed.
 This example shows how to use the first method:

@@ Line 1: / Line 1: @@
 It's possible to drive more than just one display out of the GDISP module. Each display is completely independent. The displays can have different display controllers and therefore different interfaces and also different resolutions. Note: "multiple displays" means that you can also use more than just two displays.
-A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the remote display support.
+A common purpose of this feature would be to have one main control screen and a smaller status screen. Furthermore, this can be very interesting in combination with the [[remote display]] support.
 When dealing with multiple displays, GFX distinguishes between the displays and the controller types. This is useful for when using the same type of display controller more than once so you don't have to include the code multiple times.
-The first thing to do is to specify the amount of displays and the number of different controller types in your gfxconf.h:
+The first thing to do is to specify the amount of displays and the number of different controller types in your [[gfxconf.h]]:
 <syntaxhighlight lang=c>
 #define GDISP_TOTAL_DISPLAYS		3
 #define GDISP_TOTAL_CONTROLLERS		2
 </syntaxhighlight>
-Where GDISP_TOTAL_DISPLAYS is the total amount of displays, regardless of the number of controller types, and GDISP_TOTAL_CONTROLLERS is the total amount of different display controller types. We're going to use the SSD2119 and the ILI9320 in the following example.
+Where <code>GDISP_TOTAL_DISPLAYS</code> is the total amount of displays, regardless of the number of controller types, and <code>GDISP_TOTAL_CONTROLLERS</code> is the total amount of different display controller types. We're going to use the SSD2119 and the ILI9320 in the following example.
-If you are using the same controller type for every display (GDISP_TOTAL_CONTROLLERS = 1) that is all you need to do.
+If you are using the same controller type for every display (<code>GDISP_TOTAL_CONTROLLERS = 1</code>) that is all you need to do.
-If not, you have to provide the list of drivers that are used through the GDISP_CONTROLLER_LIST macro and map the displays to them:
+If not, you have to provide the list of drivers that are used through the <code>GDISP_CONTROLLER_LIST</code> macro and map the displays to them:
 <syntaxhighlight lang=c>
 #define GDISP_CONTROLLER_LIST		GDISPVMT_SSD2119, GDISPVMT_ILI9320
 #define GDISP_CONTROLLER_DISPLAYS	2, 1
 </syntaxhighlight>
-The GDISP_CONTROLLER_DISPLAYS macro tells how many displays that have to be mapped to the corresponding displays driver from the GDISP_CONTROLLER_LIST macro. The sum of GDISP_CONTROLLER_DISPLAYS must be equal to the amount of displays specified through GDISP_TOTAL_DISPLAYS.
+The <code>GDISP_CONTROLLER_DISPLAYS</code> macro tells how many displays that have to be mapped to the corresponding displays driver from the <code>GDISP_CONTROLLER_LIST</code> macro. The sum of <code>GDISP_CONTROLLER_DISPLAYS</code> must be equal to the amount of displays specified through <code>GDISP_TOTAL_DISPLAYS</code>.
 And the last thing left to do in your gfxconf.h for multiple controller types is to specify the color format you want your application to run in. Each display controller will automatically translate it for his specifications:
@@ Line 51: / Line 51: @@
 == Board files ==
-Your board files for your controllers will need to be updated to indicate how each controller talks to each display. There is a special member g->board in the GDisplay structure that gets passed to each function. This member variable can be used by the board file to (for example) point to hardware register sets. This member is purely for the board file's use and is not touched by any other code.
+Your board files for your controllers will need to be updated to indicate how each controller talks to each display. There is a special member <code>g->board</code> in the [[GDISP#GDisplay|GDisplay]] structure that gets passed to each function. This member variable can be used by the board file to (for example) point to hardware register sets. This member is purely for the board file's use and is not touched by any other code.
-−
-−
 == Access the displays ==
-Your displays are now set up and you can access them. There are two different ways to do so. One way is to select the current active display through the gdispSetDisplay() call and use the gdispXxx() routines as you would with just one display. The other way is to use the gdispGXxx() call instead where the first parameter is always the display that shall be accessed.
+Your displays are now set up and you can access them. There are two different ways to do so. One way is to select the current active display through the <code>gdispSetDisplay()</code> call and use the <code>gdispXxx()</code> routines as you would with just one display. The other way is to use the <code>dispGXxx()</code> call instead where the first parameter is always the display that shall be accessed.
 This example shows how to use the first method:
@@ Line 132: / Line 130: @@
 == Limitations ==
-As this is more a work-in-progress feature, it is currently NOT possible to have more than one input touch device (through the GINPUT touch module).
+As this is more a work-in-progress feature, it is currently '''NOT''' possible to have more than one input touch device (through the [[GINPUT#Touchscreen|GINPUT touch]] module).