Dealing with multiple Modules and Screens - Revision history

Ratcliffe at 18:11, 21 May 2023

2023-05-21T18:11:59Z

Ratcliffe at 18:01, 21 May 2023

2023-05-21T18:01:21Z

Ratcliffe at 17:58, 21 May 2023

2023-05-21T17:58:18Z

Ratcliffe: /* Physical cubelets and "virtual" mapping to them */

2023-05-12T04:35:37Z

Physical cubelets and "virtual" mapping to them

Ratcliffe: /* The magic of TOPOLOGY_getAdjacentFacelet() */

2023-05-12T03:49:08Z

The magic of TOPOLOGY_getAdjacentFacelet()

Ratcliffe: Created page with "This page covers various topics in dealing with the eight different modules, each with three screens, in a WOWCube. Remember that each module has its own processor and screen..."

2023-05-08T03:29:39Z

Created page with "This page covers various topics in dealing with the eight different modules, each with three screens, in a WOWCube. Remember that each module has its own processor and screen..."

New page

This page covers various topics in dealing with the eight different modules, each with three screens, in a WOWCube. Remember that each module has its own processor and screens and generally does not have a "direct connection" to any of the other modules.


==Physical cubelets and "virtual" mapping to them==
Content coming soon!


==The magic of TOPOLOGY_getAdjacentFacelet()==
Content coming soon!


==How to handle moving from one screen to another (on the same or a different cubelet)==
Content coming soon!


==Dealing with differing orientation of the screens==
Content coming soon!

@@ Line 23: / Line 23: @@
        place = TOPOLOGY_getPlace(facelet);
        GFX_setRenderTarget(screen);
-       GFX_drawText([ 40,40 ], 8, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF0000FF, "module: %d", SELF_ID);
+       GFX_drawText([ 10,40 ], 10, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF0000FF, "module: %d", SELF_ID);
-       GFX_drawText([ 40,80 ], 8, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF0000FF, "screen:%d",screen);
+       GFX_drawText([ 10,80 ], 10, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF0000FF, "screen:%d",screen);
-       GFX_drawText([ 40,120 ], 8, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF00FF00, "face: %d", place.face);
+       GFX_drawText([ 10,120 ], 10, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF00FF00, "face: %d", place.face);
-       GFX_drawText([ 40,160 ], 8, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF00FF00, "position:%d",place.position);
+       GFX_drawText([ 10,160 ], 10, 0, 0, TEXT_ALIGN_LEFT_TOP_CORNER, 0xFF00FF00, "position:%d",place.position);
        GFX_render();
+     }
@@ Line 33: / Line 33: @@
 CubeOS maintains a concept of "places" which consist of a cube face (numbered 0-5) and a position on the face (numbered 0-3). The screen capture below from the emulator shows the relationships on starting an app after clicking on "0" at the upper right in the emulator to reset the cube geometry to default.
-[[File:CubeMapping.JPG|border|Cube Layout]]
+[[File:CubeMapping2.JPG|border|Cube Layout]]
 Here I will soon explain

@@ Line 33: / Line 33: @@
 CubeOS maintains a concept of "places" which consist of a cube face (numbered 0-5) and a position on the face (numbered 0-3). The screen capture below from the emulator shows the relationships on starting an app after clicking on "0" at the upper right in the emulator to reset the cube geometry to default.
-[[File:CubeMapping.jpg|border|Cube Layout]]
+[[File:CubeMapping.JPG|border|Cube Layout]]
 Here I will soon explain

@@ Line 30: / Line 30: @@
+     }
+   }
 Here I will soon explain

@@ Line 3: / Line 3: @@
 <span id="PhysicalVirtual"></span>
 ==Physical cubelets and "virtual" mapping to them==
-Content coming soon!
+<span id="AdjacencyDetermination"></span>
 ==The magic of TOPOLOGY_getAdjacentFacelet()==
 <span id="AdjacencyMovement"></span>