Ed Majcher

Sorry if this is documented somewhere, but I am new to the forum and I have come across a couple issues with 5 and I was wondering what the protocol was for posting bugs. They are not major issues but I thought I would throw them out there:

1.) Issues using Command + ~ to cycle through the documentation and open patches. It seems to work sometimes but not others. An example is that it will cycle through the documentation while you are in the Table of contents but not once you select a topic (for me a tutorial).

2.) Save on a pre-existing patch (one that has been saved already) seems to always act like a Save As and bring up the file dialog each time asking if you are sure you want to overwrite the patch, even if it is the one you are working in with the same name.

Nothing major, just some minor inconveniences.

Sorry if this is documented somewhere, but I am new to the forum and I have come across a couple issues with 5 and I was wondering what the protocol was for posting bugs.  They are not major issues but I thought I would throw them out there:

1.)  Issues using Command + ~ to cycle through the documentation and open patches.  It seems to work sometimes but not others.  An example is that it will cycle through the documentation while you are in the Table of contents but not once you select a topic (for me a tutorial).

2.)  Save on a pre-existing patch (one that has been saved already) seems to always act like a Save As and bring up the file dialog each time asking if you are sure you want to overwrite the patch, even if it is the one you are working in with the same name.

Nothing major, just some minor inconveniences.


reporting-bugs

> 2.) Save on a pre-existing patch (one that has been saved already) seems to always act like a Save As and bring up the file dialog each time asking if you are sure you want to overwrite the patch, even if it is the one you are working in with the same name.

I can't reproduce this. This will happen when you import a patcher from Max 4, since Max 5 cannot save over the Max 4 document.

> 2.)  Save on a pre-existing patch (one that has been saved already) seems to always act like a Save As and bring up the file dialog each time asking if you are sure you want to overwrite the patch, even if it is the one you are working in with the same name.

Interesting because I can reproduce this at will ... I open max 5, say new patcher, add an object (any object will do). I save it, make a change, then save again and I get the Save As dialog. I looked at the patch, it has the .maxpat extension and if I edit the file it is obviously formatted in JSON syntax. Come to think of it, I didn't see this behavior until I upgraded to 5.0.1 though.

Interesting because I can reproduce this at will ... I open max 5, say new patcher, add an object (any object will do).  I save it, make a change, then save again and I get the Save As dialog.  I looked at the patch, it has the .maxpat extension and if I edit the file it is obviously formatted in JSON syntax.  Come to think of it, I didn't see this behavior until I upgraded to 5.0.1 though.


I also cannot reproduce the save over pre-existing feature. Things that might be good to know are OS version, what the total path of the file you are saving/saving over is, if the file is in use by another application or other permissions issues are present, etc.

https://cycling74.com/twiki/bin/view/FAQs/BugReportGuidelines

And as for the issues with the Doc Browser navigation on OS X, please see recent threads on keyboard command swallowing/ignoring with the documentation window. These are artifacts of embedding Apple's WebKit which we are not sure if/when they will be resolved.

I am running os X, latest greatest, all patched up. I did some experiments and I found what the issue is/was (It didn't seem to occur until I upgraded to 5.0.1) but now that I have solved it, it is easy to work around.

I have always saved my patches to the directory (since max 4.6):

/home/majcher/production/"max/msp"/msp tutorials

I attempted saving to other directories and the save functionality worked fine ... what I did was remove the / from max/msp and named it to max msp so the new directory is:

/home/majcher/production/max msp/msp tutorials

Now it seems kind of obvious, but it was never and issue before and as a long time software developer I should have known not to use the / in the path name, but it always seemed to work in the past, probably through apple unix voodoo and escaping the "/" behind the scenes.

End result, I renamed it and it isn't an issue for me anymore, thanks for suggesting checking the full path.

I am running os X, latest greatest, all patched up.  I did some experiments and I found what the issue is/was (It didn't seem to occur until I upgraded to 5.0.1) but now that I have solved it, it is easy to work around.

> End result, I renamed it and it isn't an issue for me anymore, 

> thanks for suggesting checking the full path.

That's correct "/" is now totally forbidden in a file/folder name.

> End result, I renamed it and it isn't an issue for me anymore,  
> thanks for suggesting checking the full path.

Reporting bugs?