Stupid array question

[SteveB]

As my previous reply ratteled around in my head some more (Hard to do while chasing around my little ones on a Sunday afternoon), the method I mentioned relating to the EEPROM could be implemented with READCODE and WRITECODE as well. Definately have a look the link to Darrel Taylor's stuff. You could use the techniques he has come up with to set your initial messages, then later use the ERASECODE/WRITECODE if you want/need to change things (EDIT: But you have to write in 64 byte blocks, which should not be such a limiting factor in your case. See the Datasheet!). If you have lots of extra code space available, why not use it and avoid adding another component to the project.

Steve

[sayzer]

RUBiksCUbe,

I think you now are like a kid in a candy shop and you are allowed to get only one candy but there are hundreds of different candies around you.

You can not decide which one to get???

You came down to two choices; Lookup or EEPROM?





------------------

[RUBiksCUbe]

Lookup or EEPROM
....hmmm....

Well, I already wrote a java applet that exports designes straight to the form of Lookup tables (based off of the one used here: http://www.sparkfun.com/commerce/pre...20LED%20Client)

So for now I'll stick with Lookup, but eventually I'll run out of code space and migrate over to an EEPROM. I'm planning on having a lot of messages available to be cycled through. I guess I could just adapt my applet to export just the hex characters without the Lookup code around it for EEPROM use.

So until I run out of space, I'll stick with Lookup