Chaos in the update window

[pd]

Haha, just noticed this.
Something's wrong with the TX info format I would believe.

[Blade]

Yeah, I think its to do with the fact I edited the upd file in linux since the only ftp client I've made work is linux based. Probably an issue with the EOL format or something (LF instead of LFCR). Need to find a linux editor that lets me specify the EOL format to use.

[Electro]

Um, Gedit and Geany both allow for EOL format specification. Check the menus. Of course, if you use KDE, well, then, ask the Flying Blinking Red Head.

[Renegade]

You could, of course, just do

Code:

todos -b the_file_name

or unix2dos, depending on what your binary is called.

Ultimately, this is a Launch Base bug, imo...assuming a specific \n configuration, no matter how likely it may be, is the same as setting a list limit to 100 because it's unlikely there'll ever be that many units - it will work in most cases, but it'll break eventually.

[Marshall]

I've just put out Launch Base version 0.99.230 which will translate all UPD files' end of line characters into the expected format (CRLF) after downloading them.

The LBMC help files do mention "uploading in binary mode" but it is just a throw-away comment that simply assumes you have created the file in Windows.

[pd]

Works nicely, good job!