Multiple instances and scrolling

[patranjo]

I have two instances of the scoreboard in my setup and they both work great until one of them needs to scroll. For instance when the college side of my setup needs to scroll fist it takes about 1 or 2 minutes for it to start scrolling but when it does the pro side starts to scroll also even though there are not enough games to need scrolling. Then after a few minutes the pro side just shows the header and the games disappear. Here is the scoreboard part of my config.js file:

{
module: "MMM-MyScoreboard",
position: "bottom_left",
//classes: "default everyone",
header: "College Scoreboard",
config: {
showLeagueSeparators: true,
colored: true,
viewStyle: "stackedWithLogos",
maxHeight: 400,
scrollSpeed: 6,
sports: [
{
league: "NCAAB",
groups: ["SEC"],
teams: ["TA&M","TAMU"]
},
{
league:"NCAAF",
groups: ["SEC"],
teams: ["TA&M"]
},
{
league: "NCAAM",
groups: ["Top 25", "SEC"],
teams: ["TA&M", "TAMU"]
}

		  ]

	  }
	},
	{
                    module: "MMM-MyScoreboard",
                    position: "bottom_right",
                    //classes: "default everyone",
                    header: "Pro Scoreboard",
                    config: {
                      showLeagueSeparators: true,
                      colored: true,
                      viewStyle: "stackedWithLogos",
		  maxHeight: 400,
		  scrollSpeed: 6,
                      sports: [
                        {
                          league: "MLB",
                        },
                        {
                          league: "NFL",
                        }

                      ]

              }
            },

[dathbe]

Interesting. I implemented multiple instances and someone else implemented scroll later. I don’t use multiples in my setup so I’ll need to look at it. It’s possible there’s only one scroll calculation assuming only one module.

[dathbe]

mentioning @mikeyounge because he's the one who built the scrolling feature.

[mikeyounge]

I don’t use multiple instances either so I never considered it. As @dathbe said, there’s only one calculation. Unfortunately, I don’t have the time now to troubleshoot it.

Since it isn’t baked in to the wrapper creation, I had to pull the module from a query. If it sees two modules with the same name and one meets the calculation, it will apply the tags and calculations to everything with that module name.

I understand the reasoning behind multiple instances, but I don’t have the screen real estate, so I push it all in to one list and scroll it.

[mikeyounge]

A real quick and dirty solution would be to add an “instance” number or name to the config and add it to the class name so the query could identify it. I don’t know how @dathbe feels about adding more to the config though. Other than that, finding a way to scroll without needing queries would be a more complete solution.

[dathbe]

There is already a unique identifier for each instance of the module. The built-in this.identifier is used to track notifications as they fly around. Each notification has a payload.instanceId.

While this identifier is usually based on the order in which the instance is listed in the config file, it's not always consistent, and it may be hard to reference that dynamically in CSS.