When the menu with targets opens, it is always shown with each database expanded to show all level-1 children - is it possible to make it only show the databases collapsed. Asking because I have 20-odd focused databases, so it always involves a lot of scrolling (unless the right target was in the commonly used list at top)
I appreciate this reply won’t help you very much but what you describe does not happen for me. If I use either the
Go to or the
Move to menu items, or the corresponding shortcuts, what first displays is
Inboxes followed only by the names of any databases I have open.
It may be helpful to mention what macOS and DEVONthink versions you are using.
ah, interesting. I’m using the latest versions of both.
@Stephen_C: Are you referring to the utility popovers?
@uimike: Are you referring to the contextual menu?
Yes: sorry, I should have been clearer. I was referring to the popovers when using
I never used the popovers - but just tried and these behave normally (all collapsed, allowing expansion/collapsing). Might resort to these until we figure out why my contextuals wake up all expanded to 1st level
Jim, the Safari “Clip to Devonthink” extension is doing exactly the same - “Location” menu opens to everything expanded to level 1
That’s actually intentional to easily access the first level of destinations. Another workaround is to use additional favorites or to replicate frequently needed destinations to the top level.
Christian, I understand. I know it is very low priority (and few users) but I almost wish it could be a “hidden” preference. As I tend to use many folders at level-1 (I also use tags, custom metadata, labels, smart groups) - it gets tedious to scroll through the menu. In my case, for example, just 2 databases and the “Move To” sub-menu takes all the vertical screen space, and I tend to keep 4-6 db open (out of 20+) at a time.
For some reason the set of favorites that appear on the left sidebar is not the same as the one that appears in these “Move To”, etc sub-menus.
Looking at this issue once more: it appears there may be an inconsistency in “adding to favorites” behavior here… when I selected a database in the left sidebar and add it to favorites, it doesn’t show in the “Move To” to sub-menu as favorite. BUT, if I do the same from within the contextual menu, via the “Add To” sub-menu, then it does!! - and it also places a copy of the favorited database in the left sidebar.
@uimike: Are you adding the root of the database via the contextual menu?
@cgrunenberg: The root of a database cannot be added via Data > Add to.
@BLUEFROG Affirmative CORRECTION!! - negative!! I’m adding the databases’ inbox
I think I am getting the picture here, favorites means slightly different things depending on the context.
Left side bar favorites: can be a database root
Contextual menus: cannot be a database root
I would very slightly prefer the contextuals to allow roots, but it is very very minor, favoriting the inbox works fine
Favorite databases/documents are not used in the contextual menus, only favorite groups located in opened databases.
What exactly did you actually right-/control-click? There’s no Add To submenu in the sidebar.
I was referring to the Data menu.
Databases and groups can’t be added to the reading list but databases can be added to the favorites via the sidebar.
I am getting a better sense of how these things work finally. And I found that adding the inboxes to the favorite list works for me. The one thing that totally tripped me was when I add the INBOX for a given database, it gets added with the exact same name as the database. The inbox for database “Home” becomes “Home”. So I end up with 2 “Homes” in the left sidebar, and only one in the contextual menu “favorites” bucket - even if I knew that I had made BOTH the database (much earlier) and the inbox to favorites. And I don’t think I can change the inbox name in the left sidebar to be “Home Index”.
How I ended up like this? Because for years I just added the databases themselves (I have many) to the sidebar. I knew what was open or not (italics), and it was easy to open one when needed.
Workaround for distinguishing between database x inbox - both in the left sidebar as well as contextual menu - will be to create unique icons for them
You could rename each inbox to “Inbox [Databasename]” via the inspector.
Pete, I am assuming you have done this before, right?