Could you please refrain from posting Diagrams in Comments that crash the Diagram in the main article, so that both are dead? Perhaps you don't have this problem, but for me fetching the ads from Google slows down loading of the page enough that the betza(New).js link from the comments is processed only after the corresponding link in the article has already initialized the Diagrams (replacing the definitions by an actual board tables in the process). The original definitions are saved in an array, so the Diagram can be restored when you switch between Diagrams on the same page. But unfortunately older versions of betza.js as well as betzaNew.js reset that array while they are loaded.
I repaired this in newer versions, but by using betza(New).js?nocache=true you will be using some very old cached version. Please use nocache=42 instead. Even if this might not load the latest version in the future, at least it would load versions where I cured the interference in case of slow loading.
@HaruN Y:
Could you please refrain from posting Diagrams in Comments that crash the Diagram in the main article, so that both are dead? Perhaps you don't have this problem, but for me fetching the ads from Google slows down loading of the page enough that the betza(New).js link from the comments is processed only after the corresponding link in the article has already initialized the Diagrams (replacing the definitions by an actual board tables in the process). The original definitions are saved in an array, so the Diagram can be restored when you switch between Diagrams on the same page. But unfortunately older versions of betza.js as well as betzaNew.js reset that array while they are loaded.
I repaired this in newer versions, but by using betza(New).js?nocache=true you will be using some very old cached version. Please use nocache=42 instead. Even if this might not load the latest version in the future, at least it would load versions where I cured the interference in case of slow loading.