![]() ![]() Regarding his plans to bring 42S in sync with the latest Free42 bug fixes and enhancements, you'll have to ask the author himself. Converting everything to C# was a big task and Steve told me it took several months overall. I assume 1.4.63 was the current version when he started. In response to message #3 by Vincent Weber Message #4 Posted by Thomas Okken on, 2:55 p.m., What I can't understand is, why did he base this on Free42 1.4.63, which is a version without the TIME functions, and with two remaing bugs (ASIN and INVRT) ? Did he tell you if there is a particular reason, or if he will upgrade to the latest core any soon ?Īnyway, interesting to know that Free42 is now available, with various degrees of maturation, on every mobile plateform that has a future for sure (Symbian is dead, and we still don't know about WebOS). So, after all, somebody undertook the monstruous task to convert Free42 from C++ to C# ! :) Message #3 Posted by Vincent Weber on, 10:49 a.m., In response to message #1 by Thomas Okken Message #2 Posted by Walter B on, 1:01 a.m., Message #1 Posted by Thomas Okken on, 6:49 p.m.ĭisclaimer: I didn't create this port, and I haven't tried it myself since I don't have a WP7 phone, but I thought I'd mention it: But Windows 10 WordPad garbles README.txt, even if you tell it the file is Unicode text while opening it.Free42 for Windows Phone 7 The Museum of HP Calculators Notepad in Windows 10 handles README.txt fine, and in fact appears to use UTF-8 without BOM as its default encoding, and Visual Studio 2019 has no problems, either. (UPDATE: It looks like even Microsoft doesn't have its act together on this yet. If there are still text editors that don't recognize UTF-8 by default, that's a problem, but I think it's the text editors in question that need to be fixed, not the standards-compliant UTF-8 text files they're complaining about. other text editors have started complaining about them. Once upon a time you'd make that explicit by adding a BOM at the start of the file, but those appear to have fallen out of favor in the Windows world, i.e. The README.txt file is UTF-8-encoded, which it needs to be because Windows-1252 doesn't provide all the symbols it needs. (07-11-2021 02:36 AM)rprosperi Wrote: 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. Well, it certainly isn't hard to make the app recognize "portable." in addition to "portable". 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. Is the signal file only "portable" or is "portable." also allowed? Depending on how you make it, the file might include the trailing ".". (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. The key codes used in the Windows version's keymap.txt file are Windows Virtual Key Codes see (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. 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.įree42 (or Plus42) looks for "portable" without trailing dot, and won't recognize the file if the name does include the trailing dot. It has to be named "portable" (case insensitive) without the trailing dot. (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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |