I’m largely talking to David, who just helped me out in my other topic.
I was trying to work out why certain status file configuration commands weren’t working in my game (basically, they try to delete files the game has previously created) or worked erratically. What I found was that WinGlulxe and WinGit would not delete files the game created through them, when asked by the game, though Gargoyle would delete the files the game created through it.
The delete function is defined like this:
To delete (filename - external file):
(- FileIO_DeleteSavedGame({filename}); -).
and the similar read function works fine:
(- FileIO_LoadSavedGame({filename}); -).
as does write:
(- FileIO_WriteSavedGame({filename}); -).
So I have a definition:
The file of flagstatus is called “flagstatus”.
Then later, during runtime:
delete file of flagstatus.
I don’t know that the files were in controversial places, permission wise. For instance, moving things to the desktop often solves permission problems, rather than creates them (again, this is in Windows XP). However, if I place the gblorb on the desktop and run it in Glulxe/Git, files are created on the desktop, and can be updated there by Writing, but not deleted when the game issues the delete command.
I tried making a folder on the desktop, putting the game in there, letting the files be created in there, but Git/Glulxe would not delete them when the game was run from that folder, either. Again, Gargoyle did.
Is Gargoyle being cavalier or permissions-disrespectful? Do Glulxe/Git expect the files to be in particular places, or dislike this delete command? Or something else?
Thanks.
-Wade