Hi pico8-colleagues ...
Are you already talked about it, but I still do not understand why the printh function does not work in the pico-8 version for Windows. I do not think so complicated send messages to the console windows.
Debuguer is perhaps a more complicated to implement, but that printh work on Windows, it would help a lot. Do not you think?
Can't pass up the opportunity to throw the idea out there again:
[debugger.lua on GitHub]( https://github.com/slembcke/debugger.lua)
A single file (either .c or .lua), trivially embeddable, minimal but functional, CLI debugger with redirectable I/O. Pretty please? It won't bite.
Thanks for mentioning this again -- it was somehow missing from my bug list. Another thread describes the problem: https://www.lexaloffle.com/bbs/?tid=2549
This is now fixed for pico-8 0.1.5
The problem was that SDL2 forks pico8.exe on startup, so stdout can't reach the original console window. I'm using SDL_Log instead of printf() now under Windows.
debugger.lua does indeed look very nifty. I plan to do a more thorough review of the debugging situation near the end of alpha so will have a closer look then. At the moment the way pico-8 calls lua code is slightly quirky (mostly to allow non-blocking infinite loops), which complicates setting up things like step-wise debugging somewhat.
@slembcke, thanks for writing. I had read your post on debugger.lua, but I saw neither easy for me.
@zep, thanks for comment on this subject.
I can not wait to try the new version.
I am developing a tank game ... but I have so little free time I go slower than a turtle!
It is now working with Pico-8 0.1.5 :-).
You just need to launch the Pico-8 binary from a Command line.
You can do this simply by creating a pico_debug.bat text file in your Pico-8 directory and fill it with the following:
After that, you can double-click the pico_debug.bat file to open the command line window that will receive the debug trace and to start Pico-8.
[Please log in to post a comment]