Newly created Collection doesn’t contain anything.
There’s every possibility that this is user error / not understanding collections, but my working assumption was a collection should show all of the objects (assuming that the filter is Show All Objects), but having created a new collection it is just sitting as an empty grid.
HOW TO REPRODUCE IT
Pressed the + button in the middle of the menu.
Presented with a blank page with the Note Task Collection My Types buttons across the top.
Pressed Collection
Selected the filter, selected Objects, selected All
When complete I am presented with a blank grid (see image)
Expected the newly created Collection to show the existing objects
ADDITIONAL CONTEXT
New user so maybe user error?
SYSTEM INFORMATION
ᅟProvide your setup info:
e.g.
Macbook Air 2020
OS:
Ventura 13.5.2
Anytype Version:
v.0.34.3
Tech Info:
Device: dellagoair.local
OS version: darwin arm64 13.5.2
App version: 0.34.3
Build number: build on 2023-08-16 11:07:20 +0000 UTC from at #2815587c8afa3f81e75336226cacecb7fe105e9c(v0.27.21)
Library version: v0.27.21
Collection contains only object you put into (or “link to”), so it start empty.
Think of it as storage (a base, a shelf,…), which contains only what you put in it.
Set is like a search view, which displays all Anytype objects (filtered as required).
If you want to see all Note, you can create a set filtered by Object type : Note.
And it will contain the objects from the start (in fact, it will display them, without containing them).
So here is why I believed that a Set only showed on type.
I created a Set click the Query and it says All. If I click Object Type it tries to limit me to a specific type, so if I back out of that I am left with this view
The All is selected by default (and shows nothing), if I try to change it then I just get a list of the Types, which if I select one will return those Types. But if I set it back to All then nothing shows.
EDIT: I made a set based on Relation: Modified Date and got all of the objects to show. BUT, this is terrible UX to require a query with a dialogue box that says “Object Type / All” which doesn’t actually return All Object Types - it led me to believe that Sets were only capable of displaying one type at a time.
I agree. Honestly, I feel like the type selection in sets should be removed and only relations should be used for queries. If you want to filter a certain type, you can just use the object type relation and then add a filter anyways. Previously, you were only able to use sets by type, and only later the ability to use relations was added. So that might explain the UX issue.
Additionally, when creating a set, the query should be set too all by default imo (so you start with all objects in a set, and then can proceed to filter it using filters).