Possible bug: Tools>Collections always creates Unnamed Collection

Hi - I'm running Logos 4.5c SR-3 (4.53.0.2294) for Mac. For as long as I can remember, this has happened, so I wanted to confirm whether this was the intended behavior or a bug.

When I select Tools>Collections, I always get a blank Unnamed Collection. It always shows up under my Collection list as "Unnamed Collection". I can remove it by right-clicking and choosing delete. But then it comes back anytime I go back to the collections list via the menu bar.

What I would expect to happen is for the last opened collection to open up.

Is anyone else experiencing this?

Find more posts tagged with

Comments

Jack Hairston

When I select Tools>Collections, I always get a blank Unnamed Collection. It always shows up under my Collection list as "Unnamed Collection". I can remove it by right-clicking and choosing delete. But then it comes back anytime I go back to the collections list via the menu bar.

Hi, Rich:

This behavior is the way it is supposed to work. For details, see http://wiki.logos.com/Collections

If it makes you feel any better, the behavior was not intuitive to me, either. <grin>

RichB

https://community.logos.com/discussion/comment/383868#Comment_383868

Thanks! But unfortunately, the wiki still doesn't answer the question.

In Logos 4 go to Tools>Collections
Click “New” in the collection pane. (Getting into this habit will prevent you from accidentally changing a collection you already made.)
Replace the first text box (It will have “unnamed collection” in it) with the name you want to give your collection. For instance, if you want a collection containing all your journals, you could name it “Journals”.

What I am referring to is that there is no need to go to Step 2. In fact, it seems to make that button redundant, especially if when I go to Tools>Collections, there's already a new "unnamed collection" sitting there waiting for me, even though all I want to do is go to an existing collection.

So, if this is the intended behavior, the Wiki needs to be updated. If it's not, then perhaps someone could help fix this minor annoyance. Cheers!

Jack Caviness

https://community.logos.com/discussion/comment/383879#Comment_383879

if this is the intended behavior

It is, and it prevents the accidental deletion or modification of existing collections.

the Wiki needs to be updated

Probably

Keep Smiling 4 Jesus :)

When I select Tools>Collections, I always get a blank Unnamed Collection. It always shows up under my Collection list as "Unnamed Collection". I can remove it by right-clicking and choosing delete. But then it comes back anytime I go back to the collections list via the menu bar.

Logos designed Tools => Collections to always create an Unnamed Collection.

When a Collection is open, an option is dragging the tab to create a Favorite or Shortcut, which subsequently can be used to open a specific collection (without creating an unnamed one).

the Wiki needs to be updated

Probably

+1 [Y] that could include shortcut and Favorite option to open an existing collection. Noticed http://wiki.logos.com/Collections has had 15 contributors.

Keep Smiling [:)]

tom

Hi - I'm running Logos 4.5c SR-3 (4.53.0.2294) for Mac. For as long as I can remember, this has happened, so I wanted to confirm whether this was the intended behavior or a bug.

When I select Tools>Collections, I always get a blank Unnamed Collection. It always shows up under my Collection list as "Unnamed Collection". I can remove it by right-clicking and choosing delete. But then it comes back anytime I go back to the collections list via the menu bar.

What I would expect to happen is for the last opened collection to open up.

Is anyone else experiencing this?

Yes, this is somewhat strange. I had to think of it this way. When I first open MS Word, it too creates a blank document called Document1.

I do not follow Logos' logic by creating this blank collection that it prevents users from accidently deleting a collection.

fgh

https://community.logos.com/discussion/comment/384680#Comment_384680

I do not follow Logos' logic by creating this blank collection that it prevents users from accidently deleting a collection.

The logic is that people kept doing just that: they renamed collections and changed the rules, believing that the existing ones were already safely saved and could be opened again from the dropdown. Sort of like you can change a layout and save it under a different name, yet still open the old one from the menu. And then they realized they'd lost the old collections and got upset. I don't think I've seen any such complaints since the change, so it must work.

tom

https://community.logos.com/discussion/comment/384713#Comment_384713

I do not follow Logos' logic by creating this blank collection that it prevents users from accidently deleting a collection.

The logic is that people kept doing just that: they renamed collections and changed the rules, believing that the existing ones were already safely saved and could be opened again from the dropdown. Sort of like you can change a layout and save it under a different name, yet still open the old one from the menu. And then they realized they'd lost the old collections and got upset. I don't think I've seen any such complaints since the change, so it must work.

Oh, so we are talking about changing - not deleting. Logos has this strange thing about not letting the users save their items. They save (and do a bunch of behind the scenes processing for every key stroke. If we could make our changes and then save - everything will work out just fine.

Jack Caviness

https://community.logos.com/discussion/comment/384724#Comment_384724

Oh, so we are talking about changing - not deleting.

I did say deletion or modification [8-|]

Logos has this strange thing about not letting the users save their items.

Have noticed that trend in other software

RichB

https://community.logos.com/discussion/comment/384675#Comment_384675

When a Collection is open, an option is dragging the tab to create a Favorite or Shortcut, which subsequently can be used to open a specific collection (without creating an unnamed one).

Now *that* is a great workaround. Thanks!

And thanks to everyone else who has helped me understand a little better this idea of creating a blank document. Yeah - it doesn't totally make sense to me, but I can live with it.