Hello zep. I was wondering about a specific behavior of Picotron and I couldn't figure if it was a regression or a choice.

Prior to 0.1.0c, if a cart folder with its name ending with .p64 was loaded, saving it would preserve the format, the cart would stay a folder. Now, whatever I try to do, as soon as I save a folder cart from Picotron, it gets turned into a .p64 file, which is a bit more inconvenient as I'm currently using an external editor.

Even cp -o <src> <dest> doesn't save a folder anymore if <dest> is suffixed with .p64. Copying to a normally named folder seems to work and I just realized that as I was writing this blog post. Still my question stands.

Are project folders or files ending in .p64 will always taken as files and going to be converted as such? Was the switch intentional? Should I rename all the folders in my project folder so far?

Good luck squashing all those bugs! Have a nice day!

major regression - external editor cannot realistically work with a single pod file

+1

@freds72
You can use external editor like this in your main.lua file :
cd('/appdata/myfolder') -- folder where tour source files are
include('mycode1.lua')
include('mycode2.lua')
...Etc

Then, you can edit mycode1.lua and mycode2.lua with the code editor you like.
I must only do like this because AltGr key isn't working anymore in the last 2 versions of Picotron.

@Risike that's what we used to do and it works great until you save in Picotron for some reason (editing a GFX or something else). Then the folder gets converted into a .p64. That's the issue with that kind of workflow with versions newer than 0c.

0.1.0e update: folders suffixed with .p64 are considered back as .p64 files, saving them seems to preserve the folder. Though unprefixed folders are still being converted to .p64 on the fly but I can live with that.

Thanks for the fix!

Using this approach though I'm not seeing files reloaded upon re-run when they change externally, at least on Linux. Is this supposed to be the case?

Oof and including the last-modified time in the POD header on every write does not play nicely with source control.