f00d4tehg0dz/MMM-Jeopardy

Config

Opened this issue · 2 comments

can you please help with the times?
defaults: {
rotateInterval: 30 * 1000,
(what is this for?)
animationSpeed: 3000,
(is this 3 seconds?)
initialLoadDelay: 4250,
(can I decrease this?)
retryDelay: 5000,
(what is this?)
updateInterval: 60 * 60 * 1000
(what is this?)

I want to know which to change for how often the answers/questions are changed and how.

can you please help with the times? defaults: { rotateInterval: 30 * 1000, (what is this for?) animationSpeed: 3000, (is this 3 seconds?) initialLoadDelay: 4250, (can I decrease this?) retryDelay: 5000, (what is this?) updateInterval: 60 * 60 * 1000 (what is this?)

I want to know which to change for how often the answers/questions are changed and how.

Hey!
You revealed an issue I had with the rotateInterval and updateInterval configuration options. I have updated the code base and README to reflect the changes here:

Here is the new config and reflected comments explaining! I have removed retryDelay as it's not needed now.
FYI 100 Jeopardy questions are pulled every hour by default. I excluded that from the config, as I don't believe you'll cycle through 100 questions an hour that quickly. But if it's needed, LMK!

{
  module: "MMM-Jeopardy",
  position: "top_right",             	 // Works well anywhere
  config: {
      useHeader: false,                  // Set to True if you want a header shown
      header: "This is Jeopardy!",       // Text for Header. Only will show if useHeader is set to true in config
      maxWidth: "192px",                 // Stretch or constrain the whole container
      textAlignment: "right",            // Text alignment
      animationSpeed: 3000,              // How fast the text fades in and fades out. (e.g clue fades in and then fades out)
      initialLoadDelay: 4250,            // How soon the module loads on Magic Mirror startup, in milliseconds, 4.25 in seconds
      answerDisplayDuration: 20 * 1000,  // Duration in milliseconds to display the answer before moving to the next question (e.g 20 seconds) 
      nextQuestionDelay: 10 * 1000,      // Delay in milliseconds after displaying the answer before moving to the next question (e.g 10 seconds)
    }
},

Got it. Let me see what I can do. I may need to reconfigure some of the logic here. Give me a little bit of time