You are here:
< Back

Setup your handball scoreboard step-by-step

 

Hi!

In this short article we will show you, how can you setup your soccer scoreboard easily.

First steps::

Controller content

We will have 5 pages like on the picture.

      • Team selection
      • Score Settings
      • Signals
      • Set time
      • Set penalties.

 

Let’s do this step-by-step.

Default (start page)

On the first page (Default), we will have 2 pictures and 7 buttons.

We connect our internal datasource to the pictures.

and the pictures below, we set 4 buttons for switching between them.

We set “Call API” actions to increase or decrease the index of pictures

In addition to these, there will be 3 more buttons for “Reset all data“, go to the “Controller” page and “Set time“.

We need a “set internal datasource” webhook action with a JSON with standard data for the Reset all data button.

{
“TeamA”: 0,
“TeamB”: 0,
“period”: 1,
“teamsPictureA”: 1,
“teamsPictureB”: 1,
“timeoutsA”: 0,
“timeoutsB”: 0,
“setCurrentTime”: {
“min”: 0,
“sec”: 0
},
“setBreakTime”: {
“min”: 0
},
“setTimeoutTime”: {
“min”: 0
}
}

The “Controller” button and “Set time” have a simple “jump to” action.

e.g:

Controller

As you can see we have a lot of buttons. (Total of  22). It looks complicated, but it isn’t.

Let’s started:

  • We set on the score, period, and timeouts buttons an increase or decrease webhook.
  • The Signals and gifs navigate us with popup action to the signals page.
  • The Start Match / Pause Match /  Show and start timeout/ Start break-time buttons will have some function. (hide, show, send event)
    • Start Match: We set to this a Call API (with ‘start‘ event sent) and three Show/Hide actions to hide this and the Resume match button (if it appears)
      and also show the Stop match button.
    • Pause:  We set to this a Call API (with ‘pause‘ event sent) and a Show/Hide action to show the Resume Match button.
      e.g. Start Match button:
    • Show and start timeout: We set to this a Call API (with ‘timeout‘ event sent) and two Show/Hide actions to hide this
      and show the other Hide and start timeout button.
    • Hide and start timeout: We set to this a Call API (with ‘timeoutEnd‘ event sent) and two Show/Hide actions to hide this
      and show the other Show and start timeout button.
    • Start Break-time:  We set to this a Call API (with ‘addBreakTime‘ event sent) and two Show/Hide actions to hide this
      and show the other Stop Break-time button.
    • Stop Break-time:  We set to this a Call API (with ‘hideBreakTime‘ event sent) and two Show/Hide actions to hide this
      and show the other Start Break-time button.
    • Stop match:  We set this a Call API (with ‘stop‘ event sent, and other Call APIs for hiding widgets on the other content.)
      and seven Show/Hide actions to hide Resume, Hide and start timeout, Stop Break-time, Stop Match
      and show Start Match, Start half-time, Add overtime buttons.

Signals

We set the 13 signal button (or as much as you want) with Call API action which is to send an event to Scoreboard with the button’s name.

e.g.:

Set penalties for players

There are 24 buttons. 2-2 text widgets with background color and 1-1 user input widget. The others are transparent.

All the transparent widget has the same structure.

Penalties internal datasource:

{
“penaltieA1Player”: “0”,
“penaltieA2Player”: “0”,
“penaltieA3Player”: “0”,
“penaltieA1TimeMin”: {
“min”: 2
},
“penaltieA2TimeMin”: {
“min”: 2
},
“penaltieA3TimeMin”: {
“min”: 2
},
“penaltieB1Player”: “0”,
“penaltieB2Player”: “0”,
“penaltieB3Player”: “0”,
“penaltieB1TimeMin”: {
“min”: 0
},
“penaltieB2TimeMin”: {
“min”: 0
},
“penaltieB3TimeMin”: {
“min”: 0
}
}

Example for it:

  • 2min button
    • There will be one “Call API” action with setPenaltiePlayerA1 event
    • One jump action to go back to the Controller page
    • Two Change datasource action with overwrite property (One for setting the penalty time and one for the player number)
    • One Interact widget action for clear the input field.
    • One Execute action batch with 3 actions for hiding one user input field and the other for the buttons. (2min,4min)


Set time

This page contains 4 user inputs and 3 buttons.

Each button sends a Call API function with setBreakTime, currentTime, timeout events and they have two change datasource events also for change the value of the properties.


Scoreboard content

We need to connect datasource properties with text widgets for scores.

Also, we editing the sensor event for API calls.

All of them similar to each other, but need to change them for each controller button.

START

For the “start” event we use Execute action batch with 2 actions. (The others will be similar, so we will no longer detail this.)

Inside in the action batch

STOP

Breaktime START

(of course, we hide this when the stopper reaches the end / or we want to hide it manually)

Example for stopper events

e.g.: Breaktime stopper

Here, we use 2 kinds of event type:

  • Always
  • End (reached stop at)

The first one track the elapsed minutes and the second one for hiding widgets at the end.

Signals

All the signals event look like this, just with other audio files.

If you set all of this properly and carefully your content is finally done.