XSTR on Free42

[rprosperi]

(07-10-2021 10:51 PM)Thomas Okken Wrote:  

(07-10-2021 09:51 PM)rprosperi Wrote:  Thanks for the provision of using a signal file to allow it to be run in Windows as portable or side by side with Free42 installed. Is the signal file only "portable" or is "portable." also allowed? Depending on how you make it, the file might include the trailing ".".

It has to be named "portable" (case insensitive) without the trailing dot. It looks like Windows Explorer won't let you create a file or directory named "portable." and removes the trailing dot if you try; when I create such a file or directory from the Cygwin bash shell, it isn't displayed in Explorer.

Free42 (or Plus42) looks for "portable" without trailing dot, and won't recognize the file if the name does include the trailing dot.

(07-10-2021 09:51 PM)rprosperi Wrote:  FYI, some of the entries in the keyboard mapping table include non-ANSI ASCII characters, e.g. the first 2 entries.

The key codes used in the Windows version's keymap.txt file are Windows Virtual Key Codes; see https://docs.microsoft.com/en-us/windows...-key-codes

Thanks. Some apps will create files with the trailing dot, and apps that expect these kinds of files usually work with one, but not the other, so just checking which is desired.

Sorry I wasn't clear - I opened the README.txt file and the text editor I used complained about the invalid characters in the table shown there.