File.filename bug?

K, figured it out. Pretty sure it's a reference problem. If you don't get rid of the old file reference (with File.close) before you run a new File constructor, it will cause some problems, one of them apparently being that it messes up the filename property. Another being that it will not open the file in memory so you can write and read from it.

Check out the code below for a solution to the problem. I found it by posting all of the properties and looking for a difference between the first and the second time assigning the file. 'isopen' was 0 after the first assignment.

Here's the working code:

var patcherDir = this.patcher.filepath.replace(patcher.name+".maxpat", "");var awesomeFile;

function writeNpostname()
{
    if(awesomeFile) awesomeFile.close();
    awesomeFile = new File(patcherDir+"asauce.txt", "readwrite", ["TEXT"]);
    awesomeFile.writeline("I am the most awesome file");

//post all properties to max windowpost("access: " + awesomeFile.access);
    post();
    post("byteorder: " + awesomeFile.byteorder);
    post();
    post("eof: " + awesomeFile.eof);
    post();
    post("filename: " + awesomeFile.filename);
    post();
    post("filetype: " + awesomeFile.filetype);
    post();
    post("foldername: " + awesomeFile.foldername);
    post();
    post("isopen: " + awesomeFile.isopen);
    post();
    post("linebreak: " + awesomeFile.linebreak);
    post();
    post("position: " + awesomeFile.position);
    post();
    post("typelist: " + awesomeFile.typelist);
    post();
    post("———————————");
    post();
}