Customizing Scrollwall Event Screen
This article will demonstrate to you how our Scrollwall Event Screens work and how you can customize them.
This section will demonstrate how the Scrollwall Event Screen works. It may help you understand how issues around specific tile displays or missing tiles could arise.
The queue is where our system holds tiles that will be displayed on the event screen. It's invisible and operates in the background.

Queue
- By default, the queue has a capacity of 30 tiles. You can change the capacity by using either the Custom JavaScript or the Amount of Tiles in Loop option in the Display Options.
- A smaller queue causes a higher frequency of seeing the same tiles.
- Whenever a new tile is received, the oldest tile will be removed from the queue.
- If you use a high-velocity term for your filter in the Event Screen, it's possible that all of the current tiles could be replaced with new ones after each queue check.
The tiles in the queue will be cloned one by one to fill out all of the cells in different rows.

Queue and Grids
You might be wondering why we need to create 2 groups in one row. That's all because of the scrolling animation. We will explain this in the following section.
The following diagram illustrates how the Scrollwall animates.

Animation and Swapping
- Each tile could have different width according to its content.
- Each row could have different width according to the total width of its belonging tiles.
- Each row is animated by the CSS Transform, which loops to move it to -50% of the x-axis in 90 seconds.
- Each loop must arrive the destination at the same time. Thus, the different width of rows results in the different speed.
- When a loop finishes, we will swap the position of the 2 groups and also replace the new tiles into the previous showing group.
- The 2 groups swapping technique is required for showing an endless row.
- It's difficult to replace new tiles anytime they arrive since it might affect the row width and cause a jumpy animation.
- To avoid the above issue, we create 2 groups for swapping. When the former group arrives the destination (x:-50%), it can be swapped and updated without the issue because it has been invisible from the viewport. All you can see right now is the later group.
- At the swapping point, the later group won't be updated with new tiles since it's visible. Any visible content replacement will appear strange on the screen for the user. Thus, only the invisible group will be updated.
- Assuming that 30 new tiles arrive and are placed in the queue during the 1st and 2nd loops (The first 180 seconds). You can view the 15 new tiles from the 3rd loop.
- Will you see another 15 new tiles in the 4th loop? Well, it depends on how many new tiles are being received during the 3rd loop.
- Note that there are no new tiles being replaced in the first 180 seconds. However, you can see the new tiles every other 90 seconds from then on.
Each layout class name has a scrollWall- prefix. (We use the SUIT CSS naming convention for the Scrollwall Event Screen implementation.)

Grids