Zugg Software :: View topic

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

My package keeps resetting itself to be Read only.

When I open up my session and open the package editor it shows a little bar accross the bottom of the editor window that states this package is set as read only and there is a force save button.

I click on view -> show defaults and then rick click the tab for my package file and click properties. Then there is the checkbox for shared and one for read only.

I uncheck the shared option or the read only option then click force save.

This causes the little bar across the bottom of the window to go away but when I reopen my package the bar is back.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I had no problems turing off the read-only flag for one of my packages. You have to click the Save Changes button after unchecking the read-only to make the update. If there is a bug here it would be that it is doing the save changes after the force save, and then doesn't realize that it needs to save again. I am guessing that is what is going on from your description.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

My session package that keeps being set to read only has multiple windows inside of a single package.

If I remove all of the windows but the main window then I am able to permanently remove the read only.

To test this I opened several of the blank sessions and added a new window to them.

Close the session.

Open the session.

Open the editor and the read only option is checked and will return if you remove it, save the session, close the session, and re-open the session.

If you then delete the second window and once again un-check the read only option and SAVE then close the session and reopen it the read only option is NOT checked.

Posted: Mon Dec 03, 2007 6:20 pm

Confirmed and added to bug list. That's a really weird one.

It's a good thing I added the new read-only panel to the bottom of the settings editor. My guess is that this was happening for a long time but is just now being noticed because of that panel. And this might explain why people were having trouble with their settings not saving in some packages (if they were readonly, then they were not saving).

Wizard Joined: 22 Mar 2007 Posts: 2320

I'm seeing this bug too. In an interesting twist, I have two sessions using the same packages. One of the packages is showing this problem in one session, but not when I run the other session. I suppose the read-only flags are stored in the session package?

Wizard Joined: 17 Jun 2006 Posts: 1201

Um yeah this is the oddest bug ever. I had been using 2.14a for awhile but suddenly every time I try to do a search using View and Find it keeps saying the package is read only most of the time. Sometimes it doesn't.

Posted: Tue Dec 04, 2007 5:28 pm

No, the readonly flag is actually stored in the *.PKG file itself. But I think CMUD is activating this flag internally and causing this problem. I don't think it's actually getting saved in the pkg file like it normally does.

Novice Joined: 31 May 2007 Posts: 32