Shop OBEX P1 Docs P2 Docs Learn Events
What is the proper format for .spin files? — Parallax Forums

What is the proper format for .spin files?

Clock LoopClock Loop Posts: 2,069
edited 2010-02-20 09:44 in Propeller 1
I get this error in PropellerTool when modifying the spin file outside of PropellerTool.

-Unicode?

-Ansi?

attachment.php?attachmentid=67928
676 x 167 - 97K

Comments

  • heaterheater Posts: 3,370
    edited 2010-02-19 15:26
    The Propeller tool uses Unicode in order to be able to work with all the symbols in the Parallax font. Like resistors and capacitors etc.

    As soon as you add such a symbol it will want to store the file as Unicode text rather than ASCII so as to preserve all your nice diagrams and such.

    Personally I'd rather forgo the fancy fonts and have all my source files as ASCII.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    For me, the past is not over yet.
  • BradCBradC Posts: 2,601
    edited 2010-02-20 00:45
    Clock Loop said...
    I get this error in PropellerTool when modifying the spin file outside of PropellerTool.

    -Unicode?

    Specifically UTF-16. The Propeller tool saves the file as unicode as soon as you add any non-ASCII character to the file.

    As far as I can tell, the warning dialog is simply letting you know that it is about to double the size of your file and re-encode it in a format other than the one it was when you loaded it.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    You only ever need two tools in life. If it moves and it shouldn't use Duct Tape. If it does not move and it should use WD40.
  • Clock LoopClock Loop Posts: 2,069
    edited 2010-02-20 09:44
    heater said...
    The Propeller tool uses Unicode in order to be able to work with all the symbols in the Parallax font. Like resistors and capacitors etc.


    Personally I'd rather forgo the fancy fonts and have all my source files as ASCII.



    Not me, I LIKE the ability to use fancy fonts, and schematic symbols.

    Its not easy to include good schematics with projects in code.
    Many have tried only to end up with a file that looks wrong on end users pc's, totally useless to them.



    So looks like the answer is Unicode, thank you.
Sign In or Register to comment.