#14 Launching the scoreboard
When launching the control panel I get the following error. When looking at the scoreboard I see a large 30 over the scoreboard but everything works behind it. I am using WinXP right now with both the latest version of CHrome and Firefox
Error when calling 'createScoreBoardNodes();setupWindow();'
message: ScoreBoard.Clock(id).Running is undefined
fileName: http://localhost:8000/controls/one-operator.html
lineNumber: 79
stack: ("Jam",1)@http://localhost:8000/controls/one-operator.html:79
("Jam",1,[object Array])@http://localhost:8000/external/prototype/prototype.js:706
each((function (id) {ScoreBoard.Clock(id).Running.observe("content:change", function (event) {clockRunning(event.memo.value, $(id + "TimeTd"));});clockRunning(ScoreBoard.Clock(id).Running.getContent(), $(id + "TimeTd"));}))@http://localhost:8000/external/prototype/prototype.js:705
setupWindow()@http://localhost:8000/controls/one-operator.html:78
@http://localhost:8000/javascript/scoreboard-viewer.js:67
([object Event])@http://localhost:8000/javascript/scoreboard-viewer.js:67
name: TypeError
TypeError: ScoreBoard.Clock(id).Running is undefined
Discussion
Anonymous
You didn't mention it, but it sounds like you have updated the scoreboard.html page yourself? That is perfectly fine of course, but very useful info you should include in a bug report ;-)
From the error message, it looks like the "id" variable is probably set to a non-existent clock, although I can't tell for sure without seeing all the code. If you want to attach your updated scoreboard.html to this bug, I can take a look at it.
Oops, sorry, don't know why I was thinking scoreboard instead of the operator panel. I see where your getting an error, but I'm not sure why you would be getting that error. After you verify the problem, can you go here:
http://localhost:8000/XmlScoreBoard/scoreboard.xml
and download that XML and attach it to this bug? I want to verify that all the standard clocks are present in your XML (which they should be).
Also, you might want to try clearing your browser cache, to see if that helps.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).