Unwanted Unnamed Collection

I seem to remember something like this being an issue some time ago and thought it had been fixed. It seems that there is this persistent "Unnamed Collection" in the collections panel. Every time I delete it it returns the next time I open the panel.

Is this normal behavior? If so, can you make it stop.

Find more posts tagged with

Comments

Jerry M

can you make it stop.

What I did in Windows 7 was

1. open collections and then open an existing collection.

2. delete the unnamed collection

3. drag collections into favorites

4. then drag it from favorites to the shortcut bar

5. always open collections from the shortcut bar and never have an unnamed collection again.

Rosie Perera

They did change the behavior recently (due to user complaints) to open up to a new blank collection with the default name of "Unnamed Collection" when you open the collections panel, instead of the last collection you had opened. People were always accidentally wiping out collections they'd spent some time to build up. Now when you're faced with the new blank collection screen with that default name, if all you're wanting to do is open an existing collection, select it from the Open menu. If you want to create a new one, change the default name (Unnamed Collection) to whatever you want to call this new one.

Jerry has found a very clever workaround for this. Dragging to Favorites first and then to the Shortcut Bar is the key. That makes the shortcut open a specific collection instead of the Collections tab in general (which will once again default to the new empty collection called "Unnamed Collection").

The way they've changed things now is kind of odd because now there's no longer any need for the "New" button. Previously, the first thing you'd have to do when opening the Collections tab if you wanted to create a new collection was click New, or else you'd accidentally overwrite a previous collection. I still think the design is poor. Logos's insistence on not requiring confirmation before an accidental deletion and not requiring/allowing an intentional save after any changes are made to collections (and all sorts of other things in Logos) ends up requiring these convaluted sorts of user interfaces which either confuse or annoy people.

Jack Caviness

The way they've changed things now is kind of odd because now there's no longer any need for the "New" button.

If you open a collection and then decide you need a new one, the New button is useful. This would also apply if you are creating a series of new collections.

Rosie Perera

The way they've changed things now is kind of odd because now there's no longer any need for the "New" button.

If you open a collection and then decide you need a new one, the New button is useful. This would also apply if you are creating a series of new collections.

Ah, good point(s).

tom

They did change the behavior recently (due to user complaints) to open up to a new blank collection with the default name of "Unnamed Collection" when you open the collections panel, instead of the last collection you had opened. People were always accidentally wiping out collections they'd spent some time to build up. Now when you're faced with the new blank collection screen with that default name, if all you're wanting to do is open an existing collection, select it from the Open menu. If you want to create a new one, change the default name (Unnamed Collection) to whatever you want to call this new one.

Jerry has found a very clever workaround for this. Dragging to Favorites first and then to the Shortcut Bar is the key. That makes the shortcut open a specific collection instead of the Collections tab in general (which will once again default to the new empty collection called "Unnamed Collection").

The way they've changed things now is kind of odd because now there's no longer any need for the "New" button. Previously, the first thing you'd have to do when opening the Collections tab if you wanted to create a new collection was click New, or else you'd accidentally overwrite a previous collection. I still think the design is poor. Logos's insistence on not requiring confirmation before an accidental deletion and not requiring/allowing an intentional save after any changes are made to collections (and all sorts of other things in Logos) ends up requiring these convaluted sorts of user interfaces which either confuse or annoy people.

This is how I see the change L4 made; they only did half the job.

If we look at another program like MS Word, it too opens to a blank unnamed document. L4 now mimics this type of behavior. Now, if we open a document in MS Word, the document opens and the unnamed document is deleted. L4 does not delete the unnamed document until you close the window for collections.

All Logos had to do to prevent this odd and confusing behavior was to filter out the 'unnamed' collection if it has not been changed from the open menu.

Because Logos did not do this simple step, people, like Jerry, have to find creative ways around this odd and confusing behavior.

Jack Caviness

If we look at another program like MS Word, it too opens to a blank unnamed document.

I don't like it there. I would prefer that it open to a blank screen, but this is not a MS Word forum.

I understand why L4 opens to an unnamed collection, but showing it in the list is confusing. I agree with your suggestion.

All Logos had to do to prevent this odd and confusing behavior was to filter out the 'unnamed' collection if it has not been changed from the open menu.