write filename.llll - bug report

Discussions, advice, bug reports and much more about the "bach" environment.
Post Reply
pedrnun
Posts: 74
Joined: Sun Jan 17, 2016 3:23 am
Contact:

write filename.llll - bug report

Post by pedrnun » Sat Feb 17, 2024 7:28 pm

Dear bach developers and comunity,

It's been a while, hasn't it? :mrgreen:
Here's a bug report, for old times' sake!...

It's actually two related bugs...

Bug nr. 1 - error 5 writing filename.llll

Steps to reproduce the bug:
1 - close Max if it's open; relaunch Max;
2 - create a new patcher;
3 - create a [bach.roll] and draw some notes in it;
4 - create a message box, type "write filename.llll" in it and connect it to the [bach.roll]
5 - save the patcher (or don't);
6 - click the message box.
I get "error 5".
Now, if I open a previously saved patcher containing a [bach.roll], I am able to properly write the .llll file.
I can even close that patcher and, as long as don't close Max, I can repeat the steps above without errors -- I don't even have to save the new patcher... but the file is saved in the same folder as the last opened patcher (this is probably related to the next bug!).

Bug nr. 2 - write filename.llll saves to bach's help folder

This one took me a while to figure out...
Steps to reproduce it:
1 - open a previously saved patcher containing a [bach.roll] and a message box with text "write filename.llll";
2 - edit the contents of [bach.roll] and click the message box -- expected behaviour occurs;
3 - open the help file for [bach.roll];
4 - close it (or don't);
5 - click the message box again.
The .llll file is saved in \Documents\Max 8\Packages\bach\help.
To revert to normal behaviour, I must close and relaunch Max.

info from Max:
{
"version" : "Version 8.6.1 (b9925cf828e) (x64 windows)",
"osversion" : "Microsoft Windows 11 (build 22631), 64-bit",
(...)
"packages" : {
"bach" : "0.8.3",
"cage" : "0.7.0",
"dada" : "0.3.1",
(...)
}
}

I hope that helps!

Best,
Pedro Louzeiro

p.s. - Daniele and Andrea, now that I've (finally) finished my PhD (about Comprovisador), it's possible that you'll be seeing me a little more around here! :ugeek:

andreaagostini
Posts: 209
Joined: Fri Dec 03, 2010 1:51 pm

Re: write filename.llll - bug report

Post by andreaagostini » Sat Mar 09, 2024 10:22 am

Hi Pedro,

I think this is expected behaviour, and indeed you'll get something very similar if you try to do the same with, say, buffer~.
If you don't have a previous location set, Max will try to save in its installation folder, where you don't have write permissions. And if you open a help file, that becomes the previous location.
In general, my advice is to always specify an absolute path when you pass by a file name to write.

The only thing that puzzles me is that I don't get "error 5" but "could not save to specified location", which is a better error message indeed. I'm not sure why...

Best,
andrea

Post Reply