Text File Not Writable?

By pmj, 10 April, 2018
Forums

 

Now and then when I'm trying to export a sysex message as text I have a "not writable" error message box appear.

Let's say for example I want to call the text file "data" and write it to my desktop:

File Is Not Writable

The file "/data.txt" is not writable

If I then do "reset with default options" and try again it seems to clear this and lets me write the file.

Just wondered what the problem might be?

This is using v2.0.1.1 for OSX on a Mac running 10.13.4 (High Sierra)

Thanks!

Mark van den Berg

7 years 1 month ago

This problem has come up before (in the B-Control forum):
https://mountainutilities.eu/forums/problem-saving-presets-bc-manager-4-0

If I then do "reset with default options" and try again it seems to clear this and lets me write the file.

Restarting the program might induce the operating system to "release" the folder/file (but even this is pure speculation on my part), but I can't imagine that resetting the program's configuration has got anything to do with the "solution". Do you notice any difference in success between "Restart" and "Restart with default setup"?

   Mark.

pmj

7 years 1 month ago

Thanks Mark - "Restart" doesn't clear the problem but "Restart with Default Setup" does. 

It does seem like the issue is to do with saving files to the destop; if I get the error, don't reset the software but save the file to another drive or folder that works fine.

Among many other things, "Restart with default setup" resets the default "open" folder and the default "save" folder to the user's home folder.
So yes, in that sense it differs from "Restart".
But using "Restart with default setup" to change the saving location of an individual file is a bit like killing a fly with a cannon...
As you say, you should be able to simply select the desired folder in the save dialog box.

Unfortunately I can't reproduce your problem, at least not on my very old OS X Mavericks machine: as far as I've tried, I can save to the desktop folder (/Users/Username/Desktop) without any problems.
So I don't know what to think: maybe Apple tightened the saving restrictions in the more recent macOS versions?
But as far as I know, my applications don't behave in any special way that would cause the OS to prevent specifically them (and not other applications) from saving to the desktop.
Anyway, thanks for pointing out the problem; maybe one day I'll run into a solution, if there is one.

Mark.