David Costanzo

Commander/Editor fonts don't persist across restart for font names >14 chars

To your knowledge, has UCB Logo made any progress regarding its suitability for AI? I know nothing about UCBLogo's development plan. Would it be worth adapting FMSLogo for the future? .... and if it's worth it, what kind of enhancements would need to be planned—for of course which we lack the community resources and would instead require external funding? The idea of what's fit for the "the future" is opinion-based and debatable. Five years ago, would you have been interested in AI? Five years from...

If my calculation is correct, "DejaVu Sans Mono" is just beyond the limit of what can be read. If you can find a font with a shorter name, you can work around the bug until I have time to fix it.

Extend the build to produce an experimental installer for the 64-bit version of FMSLogo.

Daniel Ajoy writes: This is what the AI tells me. Does it make sense to you? Yes, the response makes sense. Your chatbot found a bug. Its explanation is flawed and the proposed fix isn't 100% correct because REG_SZ doesn't necessarily include a NUL terminator. In some situations, it could cause a crash. The AI response also doesn't correctly explain the impact, which is that bug only occurs if your font face name is larger than 15 characters. So "Courier New" should work. What's your font face name?...

Fix a typo in a comment

Manfred writes: I had the seemingly simple idea, FMSLogo itself could provide the root path, as it really is part of the container. You can use DLLCALL to call the win32 GetCurrentDirectoryW function. ; Calls the win32 function GetCurrentDirectoryW. ; Outputs the current working directory as a word. ; Outputs [] on error. TO GETWORKINGDIRECTORY LOCAL [rval total_characters working_directory working_directory_length] DLLLOAD "kernel32.dll ; Call it with a NULL buffer to determine the required buffer...

No,I don'see the FMSLogo window, only the scipt for a little moment, thereafter nothing. It sounds Windows can't (or is refusing) to run fmslogo.exe. I think it's worth doing the troubleshooting steps I wrote earlier. The error message from Windows would be in that script window that flashes on the screen then disappears. I expect that the output shown in the cmd.exe window will indicate the problem.