You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alternate Launcher seems to write the carriage return for the key file as LF instead of LFCR. While BMS might not care about this carriage linefeed ending using Excel Key File Editor does care about how the carriage return is defined. If its defined with just LF then importing a key file into the Key File Editor that has been written by Alternate Launcher results in Excel trying to copy the entire contents into a single cell rather than importing each line in the key file into a separate row.
Since this is a Windows tool wouldn't it be better to write the key file out with CRLF endings?
The text was updated successfully, but these errors were encountered:
Alternate Launcher seems to write the carriage return for the key file as LF instead of LFCR. While BMS might not care about this carriage linefeed ending using Excel Key File Editor does care about how the carriage return is defined. If its defined with just LF then importing a key file into the Key File Editor that has been written by Alternate Launcher results in Excel trying to copy the entire contents into a single cell rather than importing each line in the key file into a separate row.
Since this is a Windows tool wouldn't it be better to write the key file out with CRLF endings?
The text was updated successfully, but these errors were encountered: