I'm sitting at the office, messing with some potential FastLED sketches on Codebender

I’m sitting at the office, messing with some potential FastLED sketches on Codebender. (Sitting in my cubicle with an arduino and LED strip hooked up to my computer might look suspicious.) :slight_smile:

Anyway… I’m getting an error when running a modified version of the Timed Playlist. It runs on my Arduino… but gives me the following on Codebender…

(sketch file) Blink.ino:93:1: error: use of undeclared identifier ‘EVERY_N_MILLISECONDS’

EVERY_N_MILLISECONDS( 20 ) { gHue++; } // slowly cycle the “base color” through the rainbow

Any thoughts? Not a big problem if no one knows… I’ll just wait 'til I get home.

What version of FastLED is codebender using?

That’s an excellent question – I bet that’s the problem. The only thing I can find is a link to the Github page that says version 3.1 (but that’s not proof they’re running it). I also know they shut down support and library work quite a while ago when they had trouble monetizing Codebender.

It was just a way to spend a few minutes of coffee break time. Nothing that can’t wait until I get home. Maybe I should delete the whole post?

You can also always just grab the last hundred or so lines from this file and put into your code so that it’ll compile: https://github.com/FastLED/FastLED/blob/master/lib8tion.h#L1032

https://github.com/FastLED/FastLED/blob/master/lib8tion.h

Tried inserting it into different places in the code – at end, before void setup, in void setup – generates even more errors.

All good! I think Codebender’s time has past, and my coffee break definitely has. :slight_smile:

Really appreciate your attempt to help though.

If I ever need to waste a couple of minutes at work, I’ll just use Notepad++. At least that’ll keep some of my newbie coding “grammar” in order.

Plus… it’s more fun to make small tweaks to the sketch and repeatedly upload to see what kind of results I end up.

Cheers!

Wish i could do that… i cant even take my personal laptop to work so im making slower progress than a snail crossing a dessert of sand :frowning:

@Cristian_Martinez Writing sudo code on paper can still be a pretty good exercise. It will really make you think carefully how you’re going to manipulate your LED data, and I’ve found I’m more focused when I do get back to a computer and can actually type it in when I’ve done that.

  1. Hide the hardware: Get some stupid USB device like a fan, gut it and put an arduino in it.

  2. Leave hardware at home: put teamviewer on your home computer and run USB non install version of teamviewer at work. Encrypted link so IT can only tell your doing something.

Your current method is probably the most dangerous. Where I work, I.T are hopeless, but a long time ago they did compile a report of names/webpages/time spent in a one off crack down.

@Gibbedy_G They’re not THAT hardcore here… and I’M not that hardcore about sneaking it in… just like to mess around when other people would go for coffee or a smoke. A quick switch to intellectual thinking from the usual creative thinking (I work in a Creative Dept).

What’s really funny though… I have two USB fans on my desk right now. :slight_smile: (The climate control in the building is always out of whack).

Lol i work at a paper plant but security is so strict i might as well be working at DARPA cant even take a picture of the sign outside without getting fired lol