None of the lottery sites use ball images to display results, they use CSS. Kivy is not a web based framework, but the documentation indicates that there is an internal set of codes that can act like CSS.

Also, pre loading to a dictionary structure may help solve some issues along the way... 

1. No need to pre render views not used. I may not always want to view the column stats, so that data can be saved and rendered on demand. The same when using a value other than 0 in the window setting.

2. The column stats page can be generated on demand and be swiped away when done, preserving the original output!

3. The layout setup will have an easier time combining the output of bonus ball games, which are calculated separately.

I have also confirmed at the script level that the completion of updates will contribute a value of 1 to the progress meter, which is going to be scaled at 14... this way when the PA lottery drops cash 4 life, I only need to change the code in one place AND delete the button and associated csv files with an "update".

Also, each game will have 2 choices when selected... process classification or display followers. So now it will be a true framework as other systems can be added to this screen... all using the same history files! For initial simplicity, follower data will be measured using the entire history file, and the update of draw data is not automatic, in case you want to see the follower data compared to the next draw.

All of the other features will remain intact.

Two systems rolled into one app!

Windows development is right around the corner, pending results of the 14 game classification test...

Getting there, one step at a time...