Permissions error on save with Studio 2.8.1

Want to talk about something that isn't covered by another category?

Moderators: heatherlaine, Klaus, FourthWorld, robinmiller, kevinmiller

richmond62
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 2598
Joined: Fri Feb 19, 2010 10:17 am
Location: Bulgaria
Contact:

Re: Permissions error on save with Studio 2.8.1

Post by richmond62 » Fri Jan 05, 2018 9:37 am

Are you referring to earlier versions of LC or later versions of RunRev?
An early version of LC is a late version of RR as
they are the same thing beyond having their name changed.

trailboss
Posts: 112
Joined: Sat Dec 13, 2008 4:55 pm

Re: Permissions error on save with Studio 2.8.1

Post by trailboss » Fri Jan 05, 2018 4:35 pm

I guess that would be true. However, if I cannot solve this permissions problem, what's steps would be easiest to upgrade to the newest version so it will work properly on my Imac? Which LC version might I begin with to begin the process and where can I get the earlier version?

trailboss
Posts: 112
Joined: Sat Dec 13, 2008 4:55 pm

Re: Permissions error on save with Studio 2.8.1

Post by trailboss » Fri Jan 05, 2018 5:10 pm

FourthWorld wrote:
Thu Jan 04, 2018 8:04 pm
A lot of people use LC daily on macOS, so I'm sure we can help you past this hurdle.

Permissions errors in any app are usually a result of attempting to write to a file in a protected location. What is the full path where you're trying to save the stack file?

Thanks for replying. I'm not getting past the hurtle,though. The only way to use my 2.8.1 studio now is to save as with a different name each time I want to save. Any ideas? I downloaded a 2013 LC program and my stack opens and if I don't get an error, my buttons when clicked do nothing so the upgrade options isn't very easy at all. Endless code correction.

richmond62
Livecode Opensource Backer
Livecode Opensource Backer
Posts: 2598
Joined: Fri Feb 19, 2010 10:17 am
Location: Bulgaria
Contact:

Re: Permissions error on save with Studio 2.8.1

Post by richmond62 » Fri Jan 05, 2018 5:44 pm

my buttons when clicked do nothing
They must contain quite complex scripts then.

I am still using stacks I wrote in RunRev 1.1.1 with LiveCode 8.1.8
without a hitch.

The ONLY problem I ever had was converting my Devawriter Pro source files from 4.5 to 7.1 because of the
change in the way Unicode glyphs are handled.

Personally, I'd think very carefully about the functionality of the buttons and rewrite them from scratch.

trailboss
Posts: 112
Joined: Sat Dec 13, 2008 4:55 pm

Re: Permissions error on save with Studio 2.8.1

Post by trailboss » Fri Jan 05, 2018 9:06 pm

richmond62 wrote:
Fri Jan 05, 2018 5:44 pm
my buttons when clicked do nothing
They must contain quite complex scripts then.

I am still using stacks I wrote in RunRev 1.1.1 with LiveCode 8.1.8
without a hitch.

The ONLY problem I ever had was converting my Devawriter Pro source files from 4.5 to 7.1 because of the
change in the way Unicode glyphs are handled.

Personally, I'd think very carefully about the functionality of the buttons and rewrite them from scratch.
Well, perhaps you're right. It it probably time to move over to the new software since I bought the expensive license. Yes, the scripts are a mad spaghetti works.

bogs
Posts: 1920
Joined: Sat Feb 25, 2017 10:45 pm

Re: Permissions error on save with Studio 2.8.1

Post by bogs » Wed Jan 10, 2018 10:57 pm

trailboss wrote:
Thu Jan 04, 2018 7:56 pm
I'm using Studio 2.8.1 and foolishly upgraded to High Sierra on my Macintosh. All works well, but I can't save my stacks because I get a permissions error: "Can't save stack...due to an error: can't open stack backup file Check the file path, and make sure you have sufficient permissions."
I forgot to ask you, where your saving to, in the info box for that folder, do you see something like this?
Image
If so, you can make sure you have permissions to read / write that folder.

It is possible that High Sierra doesn't have this ability anymore, I have no idea, this is on OSX 10.6.6.
Image

Post Reply

Return to “Off-Topic”