Storage Unit

  • The-Con
    21st Nov 2011 Member 0 Permalink
    @Wazabi-Bros (View Post)
    It is okay. Remember to be as space efficient as possible. It also needs to be user friendly. That means it should not erase its self after being read (separate function). As for space (this is good for user friendliness), you can have the write spot the same as the read... for example, you the same line (two different materials) will read and write data.

    At some point I will see if I can make a design that will work well.

    edit:
    Here:


    I made a save to experiment the maximum number of bytes I could fit on the screen.
    420
  • Wazabi-Bros
    21st Nov 2011 Member 0 Permalink
    Wow Thanks! Um I'm sorry to bother you but for some reason i cant view your save (WHY!!) can you give me the ID
    and thanks for the great advice

    Also is it 8-Bit?
  • The-Con
    21st Nov 2011 Member 0 Permalink
    Save ID: 603820

    It is 8-bit
  • Wazabi-Bros
    21st Nov 2011 Member 0 Permalink
    Thank you! You are really helping and i would like to thank you again
  • Synergy
    21st Nov 2011 Member 0 Permalink
    Also look into using array for your memory. It is often used for memory.
  • The-Con
    21st Nov 2011 Member 0 Permalink
    @Synergy
    How exactly does that work? I have looked at saves that use array, and have even tried to come up with my own, but I don't really understand how it works. is it still using a switch based system?
  • Wazabi-Bros
    21st Nov 2011 Member 0 Permalink
    Synergy... I think your opinion is valid. Your saves are compex circitry and i love that!
    But The-Con also have complex saves so ill concider both.
    And from your last post, I should make it:
    Space efficient + userfriendly.... = manual to use